lessons learned from managing mobile team development
DESCRIPTION
I Can Lick 30 Tigers Today - presentation given by Kristina Podnar at the J. Boye Philadelphia 13 conference. Having a PMP or project management experience may qualify you for many software development projects, including the web, but mobile development team management is in a league of its own. Come and share in the discussion of lessons learned from developing mobile sites and applications for major TV networks and publishing houses. This presentation will focus heavily on how you, as a non-technical lead, can succeed in leading a technical development project.TRANSCRIPT
KRISTINA PODNAR@kpodnar
I Can Lick 30 Tigers Today Lessons Learned From Managing a Mobile App Development Team
JBoye Philadelphia – May 8, 2013
I used to think as a PM.
@kpodnar
Traditional project management skills still apply
www.nativetrust.com
Target setting Problem solving Leadership Team building Triage
Identify what is needed or has to be done
Organize resources Monitor performance and task
completion Plan ahead for future requirements Deal with any problems that arise
But mobile development is a different kind of tiger!
PM Skillset
Traditional PM Role Mobile Development PM Role
Plan-Do mindset Prepare a specific timeline and
sequence of activities Formally outline what, why, who,
how, and when Delivering on time and on budget
are the most important things
Envision-Explore-Adapt mentality User need vs. technical feasibility Lead a motivated, experienced,
and disciplined development team Focusing on delivering real
business value at all times is the most important thing
@kpodnar
Here’s what we’ll do!
Here’s what we’ll do!
What We’re Doing
www.nativetrust.com
I heard a rumor at WWDC!
I heard a rumor at WWDC!
TRADITIONAL THINKING
Paced technology changes and platform upgrades.
Greater number of examples/proofs.
Often customizations vs. development.
Requirements are (mostly?) proven.
MOBILE THINKING
Marketplace is constantly changing.
Nobody has the actual solution because you are racing not pacing (MRAID, BlueKai, UA).
New device features are released quarterly.
Often “on the fly” requirements.
What We’re Doing
@kpodnar
Requirements, design, development, testing, release!
Requirements, design, development, testing, release!
How We’re Doing It
Wash, rinse, repeat!
Wash, rinse, repeat!
www.nativetrust.com
TRADITIONAL THINKING
Initiating Planning Executing Monitoring and
Controlling Closing
MOBILE THINKING
More complicated environment drives momentum and development.
It’s a living product – we can’t get it all in one swipe.
Any release must include an SDK.
How We’re Doing It
@kpodnar
Leverage established
best practices.
Leverage established
best practices.
How We’re Delivering
www.nativetrust.com
Live in an ever-changing world.Live in an ever-changing world.
TRADITIONAL THINKING
Run through the system requirements specification.
Leverage all platforms, browsers and devices.
Weekend/off-peak releases.
MOBILE THINKING
Lack of specifications (SRS), and reliance on use cases.
Improve quality before product is complete.
UDID-based (until May 1). App store beta cycles. Can you really replicate
testing?
How We’re Delivering
@kpodnar
Key Take-Aways
www.nativetrust.com
Blend your PM “gut instinct” with new thinking
Be humble about technology Become hands on Simple costs less Sweat the little stuff Get a lucky penny
Some More Take-Aways
Objectify requirements Pair coding is highly
underrated – use it! Implement strong and
short-term incentives Use ALL of the tools you
can Sign personal OLAs Look for friends in “fast
places”
It is still a thankless job.
Go lick those tigers!
@kpodnar
Questions/Discussion - Today and After JBoye