Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Agile Product Management

6,480 views

Published on

My presentation for MageTitans on Nov 7th, 2015 in Manchester, England about create great Magento products with Agile Development Methodologies

Published in: Software, Technology
  • Nice !! Download 100 % Free Ebooks, PPts, Study Notes, Novels, etc @ https://www.ThesisScientist.com
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Hello! Get Your Professional Job-Winning Resume Here - Check our website! https://vk.cc/818RFv
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Agile Product Management

  1. 1. AGILE PRODUCT MANAGEMENT
  2. 2. Hi, I am Kimberely Thomas Managing Director interactiv4 New York, NY @magentogirl
  3. 3. This is a talk about creating GREAT PRODUCTS WITH AGILE DEVELOPMENT METHODOLOGIES
  4. 4. but first, A BRIEF INTRO TO SCRUM
  5. 5. SCRUM TEAM PLAYERS Product Owner -visionary -strategist -drives product Scrum Master -facilitator -manages the information exchange Team
  6. 6. CORE PRINCIPLES OF SCRUM —Backlog of User Stories —Sprints -Sprint Planning Meetings -Daily Scrum Meetings -Retrospective
  7. 7. USER STORIES Action Stories for the software user, that describes the type of user, what they want and why. A user story helps to create a simplified description of a requirement.
  8. 8. TOOLS -Jira -Assembla
  9. 9. REPORTING VELOCITY REPORT > know how much your team completed in hours or story points for a sprint > story points vs hours
  10. 10. REPORTING BURNDOWN REPORT > How much has burned down per sprint and how much is left to complete the product
  11. 11. BEING AGILE
  12. 12. ag·ile ˈajəl/ adjective 1. able to move quickly and easily. "Ruth was as agile as a monkey”
  13. 13. DO WHAT WORKS FOR YOUR TEAM
  14. 14. AGILE TEAM Product Manager (Product Owner) Tech Lead (Scrum Master) Team
  15. 15. Agile Methodologies Backlog -Pruned Tickets with Estimates Sprints -Tickets to be worked on Sprint Planning Meeting Daily(?) Stand up
  16. 16. TICKETS VS USER STORIES because ‘A user can view the home page as designed’ makes less sense then ‘Style the Home Page’
  17. 17. ANATOMY OF A TICKET -Summary* -Description* -Attachments* -Estimate* *REQUIRED FIELDS TO START A TICKET
  18. 18. CREATE ALL TICKETS FOR A RELEASE AT THE BEGINNING IDEALLY WITH ESTIMATES
  19. 19. TICKET WORKFLOW
  20. 20. SPRINT PLANNING MEETING > Monday AM > Prior Sprint is Closed > New Sprint is created > The TEAM picks tickets to be worked on > Tickets must be estimated > Pick tickets with a total time = your velocity
  21. 21. CASE STUDY: LACES REQUIREMENTS Have a Modern Look and Feel -Home Page -Category Page -Product Page -Checkout Have a Shoe Customizer -Allow user to select color of shoe, trim and laces -Allow user to upload logo of shoe
  22. 22. CASE STUDY: LACES TICKETS Epic: Theming -Style Home Page -Style Category Page -Style Product Page -Style Checkout Epic: Backend -Create Shoe Customizer
  23. 23. LACES SCRUM BOARD
  24. 24. WHAT DO I WITH TICKETS FROM THE PREVIOUS SPRINT THAT ARE NOT FINISHED? Only 1 Sprint at a Time Tickets from previous Sprint are moved to new Sprint
  25. 25. WHAT DO I DO IF NEW PRIORITIES COME UP DURING A SPRINT? like Magento security patches $&@#%&! ADD THE TICKET Don’t stress over not finishing all tickets in a sprint if new things come up
  26. 26. WHAT DO I DO IF RUN OUT OF TICKETS DURING A SPRINT? GO TO THE PUB? SELECT MORE TICKETS! Jira will complain but just ignore that
  27. 27. A FEW WORDS ABOUT ESTIMATES
  28. 28. ESTIMATING -Estimates are educated guesses -You have to start in the beginning even with little information -Keep refining as you learn more -Learn from your reports of estimated vs actual time how you are doing
  29. 29. JIRA TIPS 1. Create your Workflow 2. Create your Board 3. use Versions and Epics 4. log worked time 5. use the reports
  30. 30. Epics
  31. 31. EPIC BURNDOWN
  32. 32. VERSIONS
  33. 33. VERSION REPORT
  34. 34. AGILE GIT 1. TICKET IS STARTED AND STATUS SET TO IN PROGRESS 2. GIT BRANCH IS CREATED FOR TICKET BASED OF MASTER Example: 10-Shoe-Customizer
  35. 35. AGILE GIT 3. TASK IS COMPLETED AND COMMITTED, PUSHED IN FEATURE BRANCH 4. PULL REQUEST IS CREATED TO DEVELOP 5. TECH LEAD REVIEWS CODE AND APPROVES PULL REQUEST or it is reopened
  36. 36. AGILE GIT 6. CODE IS DEPLOYED TO DEV SERVER AND TICKET STATUS IS SET TO TEST 7. IF TESTS PASSED TICKET IS SET TO READY or it is reopened
  37. 37. AGILE GIT 8. RELEASE DEPLOYMENT MERGES ALL READY TICKETS TO MASTER 9. TAG IS CREATED IN GIT AND CODE IS DEPLOYED TO PRODUCTION
  38. 38. WHAT NOT TO DO WHEN BEING AGILE?
  39. 39. Don’t Make 1 sprint and reuse it
  40. 40. Don’t skip estimating your tickets
  41. 41. Don’t use Jira for just ticket management
  42. 42. Don’t skip making tickets (never use a spreadsheet!)
  43. 43. BENEFITS OF AGILE?
  44. 44. Can always see the sprint status at a glance
  45. 45. Can easily determine when the product will be completed using the reports
  46. 46. HAPPY DEVELOPERS
  47. 47. SPECIAL THANKS TO MY TEAM AT INTERACTIV4 NYC FOR THEIR PARTICIPATION IN DEVELOPING OUR AGILE PROCESS

×