Product Council Approval EOY Review Q2. Produ ct Counc il: Appro val. PM + UX: Likely Case. Y e s. il: Conce pt N. Sprint Planning

Transcription

1 WELCOME!

2 Process Overview

3 Process End-to-End Client, Research, Market, Sales, Support R Responsible W h o t a s k? A Accountable W i s d o i n g t h e h o m a k e s t h e d e c i s i o n a n d h a s u l t i m a t e o w n e r s h i p? Prioritization Epics, Big Projects, Featurettes PM: RA UX: R CXO: I VPX: I PM Communication Bug Fixes from Support UX/Design Prototype: UX: RA Dev Mg: C PM: C All item s Prioritize d, scrubbe d Produ ct Owner Backlog Grooming PO: RA PM: C Dev: R UX: C Story Point Sizing Story Breakdown Acceptance Criteria Reprioritization Roadmap (On Cycle): Yearly Roadmap Epic (Off Cycle): Prod. Counc PM il: Conce pt N o Executable Prioritization Stories Check with Points Product Council Approval EOY Review Q2 -Biz Case -T-shirt Sizing -Audience, Potential -SWOT -Voting -Initial Backlog Unfinished Work Sprint Planning PO: R Scrum Master: C Dev: A UX: C PM: I Review Top Stories Including Exit Criteria Commit Ready Sprint In Progress Ongoing Days 3 4 Day 5 Days 6 15 Day 1 Day 2 Y e s PM + UX: Likely Case Produ ct Counc il: Appro val N o Consolid ated Backlog Stand Up SM: RA Dev: RA PO/PM : C Done 3 questions: Yesterday? Today? Blockers? Product Council: Product Mgmt R Exec Team A Dev Manager C Dev Team - I Leadership Committee (by Product): PM RA Dev Lead C Support Lead C Services Lead C Sales Engineer - C PM Recurring: Product Product Council: Council: Leadership Leadership Monthly Monthly Committee: Committee: Roadmap Roadmap Week Week 1 of 1 of Review Review & & Sprint Sprint (~3 (~3 Epic Epic (Off (Off weeks) weeks) Cycle) Cycle) Sprint Review PO: A SM: C Dev: R PM: C Velocity List of Done (accepted) stories Demos Retrospective Dev: R SM: A PM: C PO: C CXO: I Review: What went well? Poorly? Definition of Done Root Cause

4 Simplified Product Management View New In Process Engineering Ready Produ ct Mgmt Suppo rt Enhancements Bugs/Issues Stories Epics Epic Breakdown Resource Allocation Red Team Engineeri ng Spikes Chores Blue Team November 14,

5 My Asks of Product Management Always Have 2 Weeks of Cream Pull Only Resources/Time that you Need No Interruptions In Sprint Everything in the Backlog is Sized (Points) Well Groomed Backlog November 14,

6 Simplified Development View Selected Product Backlog Item Every 24 hours Daily Scrum New functionality is demonstrated at end of Sprint Sprint Backlog Sprint Product Backlog: Emerging prioritized requirements Sprint Planning November 14,

7 Task Board Story To Do In Process To Verify Done As a user, I 3 points 4 3 DC 3 Test the SC 4 DC 3 Test the 8 7 Test the 8 SC 5 Test the 8 3 Test the 3 Test the 9 Test the 9 As a user, I 7 points 4 3 DC 7 4 Test the 8 7 Test the 8 DC 7 7 November 14,

8 My Asks of Engineering Be Comfortable with Estimates Make a Commitment Take a Task, Complete a Task DWYSYWD Pull only Information / Resources that You Need Learn & Improve Contribute Have Fun! November 14,

9 Slow Down To Speed Up 1d 1d YOUR TIME! 10 days Release 10 days Review Retro Groom Planning November 14,

10 A Quote Plans are of little importance, but the act of planning is essential. Winston Churchill November 14,

11 Keys to the Process 1. Well Categorized, Prioritized and Well Defined Product Backlog (Consistent) 2. Successful Delivery on Team Commitments (DWYSYWD) 3. Better & More Consistent Estimation 4. Quality (DoD, DevOps) 5. Sound Technical and Architectural Decisions 6. Teamwork and Collaboration November 14,

12 Product Management Meetings & Artifacts November 14,

13 What is an Epic? DESCRIPTION Epics are large initiatives or projects, typically describing multiple use cases. Epics also layout the vision and business case for the initiative and provide enough detail and information to allow for a budget estimate and ranking. Epics are added to the backlog by Product Management and approved for dissemination into User Stories via the Product Council DURATION > 1 iteration READY CRITERIA Value Proposition / Story Business Case Potential Revenue Cost Savings Cost of Not Budget Estimate Risks & Assumptions Actors / Use Cases Defined Market Analysis Business Signoff (Council) Architectural Review/Signoff Decisions Diagrams * DEVELOPMENT WILL NOT PLAN OR BUILD DIRECTLY AGAINST EPICS November 14,

14 What is a User Story? DESCRIPTION User Stories define the implementation of a set of features. They describe how a user (or system) interacts with the product and the desired behaviors (Conditions of Acceptance). User Stories are added either by PM or PO DURATION <= 1 Iteration READY CRITERIA Conditions of Acceptance User Story Use Case Diagram Stack Ranking Technical Dependencies Feature Dependencies LOE UX/UI Design Sizing (Points) * Only The highest Ranked Stories in the Ready State are available for Planning November 14,

15 What is an Feature/Enhancement? DESCRIPTION Enhancements change or extend existing production feature functionality to meet a revised set of requirements. They are added by Product Management through the PO. READY CRITERIA Current Behavior Expected Behavior Conditions of Acceptance LOE Stack Ranking Sizing (Points) DURATION 1 hour 1 iteration * Only The highest Ranked Enhancements in the Ready State are available for Planning November 14,

16 What is an Issue/Bug? DESCRIPTION Issues / bugs are identified defects with existing production features. They are initially created by Customer Support. They are validated through the PO and added to the backlog when the only solution requires a Development Resource READY CRITERIA Priority (Based on Criteria) Detailed Description Steps to Repro Images/Video Stack Ranking Customer Specific Details Sizing (Points) DURATION 1 to 24 hours November 14,

17 What is an Spike? DESCRIPTION Spikes are a timeboxed activity meant to reduce or eliminate technical risk of some other backlog item that will be delivered in the future. They are typically an exploration of a new systems, infrastructure, technologies, integrations or a familiarization with existing ones. Spikes are determined and added by the technical team through the PO READY CRITERIA Timebox Expected Results Dependent PBLI s Stack Ranking Sizing (Points) DURATION 1 to 10 days - Timeboxed November 14,

18 What is an Chore? DESCRIPTION A Chore is a technical task or set of tasks typically meant to remediate technical debt, clean up, stabilize or simplify the code base. Chores are determined by the team and added to the backlog through the Product Owner DURATION < 1 iteration READY CRITERIA Description Business Case Cost of Not Cost Savings Potential Revenue Stack Ranking LOE Risks Dependencies Architectural Review Decisions Diagrams Sizing (Points) November 14,

19 Technical Planning Meeting DESCRIPTION Occurs during Planning Week. Product Manager schedules meeting to do a final review of the Backlog Items he/she would like to move to the Ready State. Only SME s in the specific Backlog items and the PO should be invited to the meeting. READY CRITERIA Break Down Epics Validate Estimates Validate Sizing Technical Risks and Assumptions Dependencies Anything else to meet Readiness Criteria DURATION 2-4 hours November 14,

20 Review Meeting DESCRIPTION Pass or Fail Each Item Capture Enhancements Occurs during Planning Week. Product Manager will be presented the output of all committed work from the previous iteration. Product Manager and PO will formally accept or reject each committed Backlog Item from the previous spring. DURATION 2-4 hours November 14,

21 Engineering Meetings & Artifacts November 14,

22 Planning Meeting DESCRIPTION Occurs during Planning Week. Engineering Team will pull ONLY Ready Stories & Enhancements from the backlog for planning. Planning will entail generating all technical tasks required to complete each item in a way that meets the team DoD and estimating each task (Team Estimation). Team commits to each delivering each Backlog Item that is planned for to meet all defined COA. Task each Backlog item Estimate each Task Commit to Delivering item Ask Questions DURATION 2-4 hours November 14,

23 Sprint Artifacts Sprint Burndown Cards Scrum Board Backlog Item Templates Additional Information November 14,

24 Other Keys to the Process 1. DevOps Session Later this Week 2. Support Pipeline, Escalation and Feedback Process Session Later this week 3. COA and Pass/Fail 4. Tools & Technology 5. Timeboxing 6. Just Enough and Pull Concepts 7. Adjust and Adapt (Retrospective > Rules & DoD) November 14,

25 Time to Play Darts! November 14,