Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Lessons Learned From Managing Mobile Team Development

484 visualizaciones

Publicado el

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.

  • Inicia sesión para ver los comentarios

  • Sé el primero en recomendar esto

Lessons Learned From Managing Mobile Team Development

  1. 1. KRISTINA PODNAR@kpodnarI Can Lick 30 Tigers TodayLessons Learned From Managing a Mobile App Development TeamJBoye Philadelphia – May 8, 2013
  2. 2. I used to think as a PM.@kpodnar
  3. 3. Traditional project management skills still Target setting Problem solving Leadership Team building Triage Identify what is needed or has to bedone Organize resources Monitor performance and taskcompletion Plan ahead for future requirements Deal with any problems that ariseBut mobile development is a different kind of tiger!
  4. 4. PM SkillsetTraditional PM Role Mobile Development PM Role Plan-Do mindset Prepare a specific timeline andsequence of activities Formally outline what, why, who,how, and when Delivering on time and on budgetare the most important things Envision-Explore-Adapt mentality User need vs. technical feasibility Lead a motivated, experienced,and disciplined development team Focusing on delivering realbusiness value at all times is themost important thing@kpodnar
  5. 5. Here’s what we’lldo!Here’s what we’lldo!What We’re Doingwww.nativetrust.comI heard a rumor atWWDC!
  6. 6. TRADITIONAL THINKING Paced technology changes andplatform upgrades. Greater number ofexamples/proofs. Often customizations vs.development. Requirements are (mostly?)proven.MOBILE THINKING Marketplace is constantly changing. Nobody has the actual solutionbecause you are racing not pacing(MRAID, BlueKai, UA). New device features are releasedquarterly. Often “on the fly” requirements.What We’re Doing@kpodnar
  7. 7. Requirements, design,development, testing,release!Requirements, design,development, testing,release!How We’re Doing ItWash, rinse,repeat!Wash, rinse,repeat!
  8. 8. TRADITIONAL THINKING Initiating Planning Executing Monitoring and Controlling ClosingMOBILE THINKING More complicated environmentdrives momentum anddevelopment. It’s a living product – we can’tget it all in one swipe. Any release must include anSDK.How We’re Doing It@kpodnar
  9. 9. Leverageestablished bestpractices.Leverageestablished bestpractices.How We’re Deliveringwww.nativetrust.comLive in an ever-changing world.
  10. 10. TRADITIONAL THINKING Run through the systemrequirementsspecification. Leverage all platforms,browsers and devices. Weekend/off-peakreleases.MOBILE THINKING Lack of specifications (SRS),and reliance on use cases. Improve quality before productis complete. UDID-based (until May 1). App store beta cycles. Can you really replicate testing?How We’re Delivering@kpodnar
  11. 11. Key Blend your PM “gut instinct” withnew thinking Be humble about technology Become hands on Simple costs less Sweat the little stuff Get a lucky penny
  12. 12. Some More Take-Aways Objectify requirements Pair coding is highlyunderrated – use it! Implement strong andshort-term incentives Use ALL of the tools youcan Sign personal OLAs Look for friends in “fastplaces”It is still a thankless job.Go lick those tigers!@kpodnar
  13. 13. Questions/Discussion - Today and AfterJBoye