'

Agile Product Management

Понравилась презентация – покажи это...





Слайд 0

AGILE PRODUCT MANAGEMENT


Слайд 1

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


Слайд 2

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


Слайд 3

but first, A BRIEF INTRO TO SCRUM


Слайд 4

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


Слайд 5

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


Слайд 6

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.


Слайд 7

TOOLS -Jira -Assembla


Слайд 8

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


Слайд 9

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


Слайд 10

BEING AGILE


Слайд 11

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


Слайд 12

DO WHAT WORKS FOR YOUR TEAM


Слайд 13

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


Слайд 14

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


Слайд 15

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


Слайд 16

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


Слайд 17

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


Слайд 18

TICKET WORKFLOW


Слайд 19

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


Слайд 20

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


Слайд 21

CASE STUDY: LACES TICKETS Epic: Theming -Style Home Page -Style Category Page -Style Product Page -Style Checkout Epic: Backend -Create Shoe Customizer


Слайд 22


Слайд 23

LACES SCRUM BOARD


Слайд 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

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

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

A FEW WORDS ABOUT ESTIMATES


Слайд 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

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


Слайд 30

Epics


Слайд 31

EPIC BURNDOWN


Слайд 32

VERSIONS


Слайд 33

VERSION REPORT


Слайд 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

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

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

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


Слайд 38


Слайд 39

WHAT NOT TO DO WHEN BEING AGILE?


Слайд 40

Don’t Make 1 sprint and reuse it


Слайд 41

Don’t skip estimating your tickets


Слайд 42

Don’t use Jira for just ticket management


Слайд 43

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


Слайд 44

BENEFITS OF AGILE?


Слайд 45

Can always see the sprint status at a glance


Слайд 46

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


Слайд 47

HAPPY DEVELOPERS


Слайд 48

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


Слайд 49


×

HTML:





Ссылка: