The document outlines a talk by Kimberely Thomas on agile product management, highlighting the Scrum methodology and its key roles such as the product owner and scrum master. It discusses the process of managing user stories, sprint planning, and ticket management using tools like Jira while offering practical tips and case studies related to agile practices. The benefits of agile are emphasized, including visibility of sprint status and improved team satisfaction.

1. AGILE PRODUCT
MANAGEMENT

2. Hi, I am Kimberely Thomas
Managing Director
interactiv4
New York, NY
@magentogirl

3. This is a talk about creating
GREAT PRODUCTS WITH AGILE
DEVELOPMENT METHODOLOGIES

4. but first,
A BRIEF INTRO TO SCRUM

5. SCRUM TEAM PLAYERS
Product Owner
-visionary
-strategist
-drives product
Scrum Master
-facilitator
-manages the information exchange
Team

6. CORE PRINCIPLES OF SCRUM
—Backlog of User Stories
—Sprints
-Sprint Planning Meetings
-Daily Scrum Meetings
-Retrospective

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. TOOLS
-Jira
-Assembla

9. REPORTING
VELOCITY REPORT
> know how much your team completed
in hours or story points for a sprint
> story points vs hours

10. REPORTING
BURNDOWN REPORT
> How much has burned down per sprint
and how much is left to complete the
product

11. BEING AGILE

12. ag·ile
ˈajəl/
adjective
1. able to move quickly and easily.
"Ruth was as agile as a monkey”

13. DO WHAT WORKS FOR
YOUR TEAM

14. AGILE TEAM
Product Manager (Product Owner)
Tech Lead (Scrum Master)
Team

15. Agile Methodologies
Backlog
-Pruned Tickets with Estimates
Sprints
-Tickets to be worked on
Sprint Planning Meeting
Daily(?) Stand up

16. TICKETS VS USER STORIES
because
‘A user can view the home page as designed’
makes less sense then
‘Style the Home Page’

17. ANATOMY OF A TICKET
-Summary*
-Description*
-Attachments*
-Estimate*
*REQUIRED FIELDS TO START A TICKET

18. CREATE ALL TICKETS FOR A RELEASE
AT THE
BEGINNING
IDEALLY WITH ESTIMATES

19. TICKET WORKFLOW

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. 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. CASE STUDY: LACES TICKETS
Epic: Theming
-Style Home Page
-Style Category Page
-Style Product Page
-Style Checkout
Epic: Backend
-Create Shoe Customizer

24. LACES SCRUM BOARD

25. 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

26. 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

27. 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

28. A FEW WORDS ABOUT ESTIMATES

29. 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

30. JIRA TIPS
1. Create your Workflow
2. Create your Board
3. use Versions and Epics
4. log worked time
5. use the reports

31. Epics

32. EPIC
BURNDOWN

33. VERSIONS

34. VERSION
REPORT

35. 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

36. 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

37. 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

38. AGILE GIT
8. RELEASE DEPLOYMENT MERGES
ALL READY TICKETS TO MASTER
9. TAG IS CREATED IN GIT AND CODE
IS DEPLOYED TO PRODUCTION

40. WHAT NOT TO
DO WHEN BEING
AGILE?

41. Don’t Make 1 sprint and reuse it

42. Don’t skip estimating your tickets

43. Don’t use Jira for just ticket management

44. Don’t skip making tickets
(never use a spreadsheet!)

45. BENEFITS OF
AGILE?

46. Can always see the sprint status at a glance

47. Can easily determine when the product will be completed
using the reports

48. HAPPY DEVELOPERS

49. SPECIAL THANKS TO MY TEAM AT INTERACTIV4 NYC
FOR THEIR PARTICIPATION IN DEVELOPING OUR AGILE PROCESS