The Devbridge Way: Lean Requirements, Rapid Prototyping, Dual-track Scrum and Scrum at Scale
10 likes1,925 views
The document outlines the Devbridge Group's engineering approach, highlighting methodologies such as dual-track Scrum and rapid prototyping to enhance user understanding and software delivery. It presents various tools and processes, including story maps and user interviews, aimed at streamlining collaboration and reducing rework. Upcoming events related to agile practices and rapid prototyping are also mentioned, emphasizing continued learning and adaptation in agile environments.
The Devbridge Way: Lean Requirements, Rapid Prototyping, Dual-track Scrum and Scrum at Scale
- 3. Our Approach Story Map Wireframe Mockup Prototype Develop IteratePlan Launch
- 4. Speakers John Ciecholewski Product Manager Laura Albun Product Manager Elijah Chang Sr. Product Manager Bill Cronin PMO Director
- 7. Goals of Lean Requirements User Empathy Shared Understanding Aligned Priorities Release Strategy
- 11. Defining Personas Grounds Keeper Course Superintendent Needs access to objective information Needs to reduce resource consumption Enhanced credibility Installer Contractor Course Architect Quantifies Value Enhanced Credibility Increased Preparation Agronomist Golf Course Crew Golf Course Builder Golfer Wants a Fun Game Golfer Wants a Low Cost Game Caddy Archetype Users Needs & Challenges
- 12. Personas
- 13. Story Map
- 14. Story Map
- 15. Story Map
- 16. Story Map
- 17. Story Map
- 18. Release Plan V2 180 pts V3 90 pts V1 290 pts Alpha Release Beta Release RTM
- 19. Parking Lot
- 20. 20
- 21. Other Tools
- 22. User Interviews
- 24. Concept Map
- 25. Site Map
- 26. Flow Diagram
- 27. Sequence Diagram
- 28. Keep Your Goals in Mind User Empathy Shared Understanding Aligned Priorities Release Strategy
- 30. Why Prototype? Form an Idea Get Approval Secure Funding Get Feedback
- 31. Sketches
- 32. Wireframes
- 36. CIBC
- 37. Story Map
- 38. Flow Diagram
- 39. Page Flow
- 40. Wireframes
- 41. Mockups
- 42. Prototype
- 43. 3 WEEKS 1 DAY 6 DAYS 8 DAYS WORKSHOP DESIGN PROTOTYPE Prototype Duration Funding Secured!!!
- 45. Dual-track Scrum
- 46. Dual Track Origins Marty Cagan cites Jeff Patton for introducing the term Dual-Track Scrum. Dual-Track Scrum is an organizational structure separating the effort to deliver working software from the effort to understand user needs and discover the best solution.
- 49. Dual Track Teams STEADY STATEEARLY SPRINTS 100% 50% 0% Time Delivery Work Discovery Work
- 51. Traditional Scrum Sprint ScopeProduct Backlog Priority H L
- 52. Traditional Scrum Sprint 1 - 4 weeks IterationSprint ScopeProduct Backlog Standup Daily Priority H L
- 53. Traditional Scrum Sprint 1 - 4 weeks Iteration Releasable Software Sprint ScopeProduct Backlog Standup Daily Priority H L
- 54. How Dual-Track Scrum Works Product Backlog
- 55. How Dual-Track Scrum Works Product Backlog UnvalidatedBacklogValidatedBacklog
- 56. Discovery How Dual-Track Scrum Works Discovery Backlog Product Backlog UnvalidatedBacklogValidatedBacklog
- 57. Discovery How Dual-Track Scrum Works KanbanDiscovery Backlog Product Backlog UnvalidatedBacklogValidatedBacklog
- 58. Discovery How Dual-Track Scrum Works Kanban Validated IdeasDiscovery Backlog Product Backlog UnvalidatedBacklogValidatedBacklog
- 59. Delivery How Dual-Track Scrum Works Delivery Backlog Discovery Kanban Validated IdeasDiscovery Backlog Product Backlog UnvalidatedBacklogValidatedBacklog
- 60. Delivery How Dual-Track Scrum Works ScrumDelivery Backlog Sprint 1 - 4 weeks Discovery Kanban Validated IdeasDiscovery Backlog Product Backlog UnvalidatedBacklogValidatedBacklog
- 61. Delivery How Dual-Track Scrum Works Releasable SoftwareScrumDelivery Backlog Sprint 1 - 4 weeks Discovery Kanban Validated IdeasDiscovery Backlog Product Backlog UnvalidatedBacklogValidatedBacklog
- 62. 62 Ideas get entered in the backlog Backlog Ready In Progress Review Done
- 63. 63 Idea gets groomed Backlog Ready In Progress Review Done
- 64. 64 Discovery team does work Backlog Ready In Progress Review Done
- 65. 65 Team reviews findings Backlog Ready In Progress Review Done
- 66. 66 Ideas are Validated (or not) Backlog Ready In Progress Review Done
- 67. 67 Delivery team works on validated ideas Delivery Backlog Sprint Scope In Progress Review Done
- 68. 68 Delivery team commits to a sprint Delivery Backlog To Do In Progress Review Done
- 69. 69 Work is done in priority order Delivery Backlog Sprint Scope In Progress Review Done
- 70. 70 Always be testing Delivery Backlog Sprint Scope In Progress Review Done
- 71. 71 Minimize work in process Delivery Backlog Sprint Scope In Progress Review Done
- 72. 72 Get to done as fast as possible Delivery Backlog Sprint Scope In Progress Review Done
- 73. 73 Sprint success, deploy Delivery Backlog Sprint Scope In Progress Review Done
- 74. When to Dual-Track Scrum Waterfall Dual-Track Small Large ProductScope Not Well Defined Well Defined Product Definition Kanban
- 75. 75 Dual Track Benefits Reduce Rework Focused Teams Better Planning Get More Done Faster
- 79. 79 Custom boards
- 84. 84 Traceability
- 86. Scrum at Scale
- 87. Scaling Teams Program Steering Committee Product Manager Release 1 Release 2 Release 3 Release 4Release Manager Architect Portfolio Business Roadmap Architecture Roadmap Portfolio Managers Investment Themes DevOps Infrastructure Security
- 88. TeamsTeams Scaling Teams Portfolio Program Business Roadmap Architecture Roadmap Steering Committee Product Manager Portfolio Managers Release 1 Release 2 Release 3 Release 4Release Manager Architect Investment Themes DevOps Infrastructure Security Teams Product Owner Sprint13 Sprint12 Sprint11 Sprint10 Sprint9 Sprint8 Sprint7 Sprint6 Sprint5 Sprint4 Sprint3 Sprint2 Sprint1 Development Team Scrum Master Designer
- 89. • Delivery dates are frequent • Delivery dates are fixed • Cargo is flexible • Quality is non-negotiable • Develop on Cadence • Deliver on demand Agile Release Train
- 90. Feature Teams vs. Component Teams Frontend Backend Database Frontend Backend Database Component Teams Feature Teams
- 91. Feature Teams vs. Component Teams Component Teams 20% Feature Teams 80% High Low Low High TechnologySpecialization Number of Teams that Use it
- 92. Ceremonies at Scale Team Sprint Planning Daily Standup Backlog Grooming Sprint Demo Sprint Retrospective Program Program Roadmap Release Planning Scrum of Scrums Change Governance Marketing Coordination Portfolio Advisory Board Business Roadmap Budget Planning
- 93. Leverage Metrics to Embrace Transparency 50 60 40 30 20 10 0 May 24 May 26 May 28 May 30 Jun 1 Jun 3 Today RemainingWork(StoryPoints) Date To Do In Progress Ideal Trend
- 94. Leverage Metrics to Embrace Transparency 0 10 20 30 40 50 60 Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6 StoryPoints Iteration Started Finished Rolling Average
- 95. Leverage Metrics to Embrace Transparency 0 25 50 75 100 125 150 Sprint 0 Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6 Sprint 7 Sprint 8 Sprint 9 Sprint 10 StoryPoints Iteration Actual Burnup Forecasted Burnup Scope
- 96. Roadmap Planning
- 97. Roadmap Planning
- 98. Work Towards Common Business Goals
- 99. Keys to Successfully Scaling Agile Good Communication Transparency through Metrics Agile Mindset Desire to Improve
- 100. Questions?
- 101. Upcoming Events ITA Tech Talk: Rapid Prototyping 2.0 Hosted by Devbridge Group October 4th 11:30 am - 1:00 pm Mobile on Tap Hosted by Devbridge Group November 9th 6:00 pm - 8:00 pm Agile Day Chicago Hosted by Morningstar November 4th 8:00 AM – 4:30 PM