Toolset For Creating a Potentially Shippable Product Increment - A session at LAST Conference 2015
•
0 likes•312 views
Many organizations compromise on the quality of product in pursuit of quick time to market and in greed of cramming more features in. The end result is the exact opposite of a “shippable product increment” at the end of each Sprint. Tactics like employing several hardening sprints towards the end of release cycle to prepare the product for release are far too common. In a way, this anti-pattern bemoans a waterfall approach and is in total contrast to the Agile Manifesto and the Principals behind the Agile Manifesto. In this talk, we will discuss the set of tools that an agile team can employ to continue delivering a potentially shippable product increment at the end of every Sprint.
Recommended
Recommended
More Related Content
Similar to Toolset For Creating a Potentially Shippable Product Increment - A session at LAST Conference 2015
Similar to Toolset For Creating a Potentially Shippable Product Increment - A session at LAST Conference 2015 (20)
Recently uploaded
Recently uploaded (20)
Toolset For Creating a Potentially Shippable Product Increment - A session at LAST Conference 2015
- 1. MOHAMMAD NAFEES SHARIF BUTT @mnsbutt
- 2. ❑Mohammad Nafees Sharif Butt ❑ http://au.linkedin.com/in/mnsbutt ❑ https://twitter.com/mnsbutt ❑Experience ❑ ~5 years as Agile Coach / ScrumMaster (10 years in SDLC) ❑ Certified Scrum Professional (CSP) ❑ PMI-ACP, Certified LeSS Practitioner ❑ PMP, CSSLP, TOGAF 9, ITIL v3 Foundation ❑Assignments ❑ ScrumMaster (Viator – TripAdvisor), Director IT (Waseel ASP Ltd.) ❑ Founder & Organizer - Riyadh Agile & Scrum User Group ❑ Presented at: Agile ME Summit 2015, Agile Australia, Global Scrum Gathering Shanghai Speaker Bio 2
- 3. ❑Problem Statement ❑Symptoms ❑Recommendations ❑Questions & Answers Agenda 3
- 4. ❑Market Trend • Lean Startups • Disruptive Innovation ❑Forces at Work • Time To Market (TTM) • Lead Time • Minimum Viable Product (MVP) • Minimal Marketable Product (MMP) Problem Statement 4
- 5. ❑Accrue Technical Debt ❑Technical Debt Classification1 Problem Statement(cont’d) 5
- 6. ❑Design Stamina Hypothesis2 Problem Statement(cont’d) 6
- 7. ❑Not being able to demo a feature ❑N+2 Sprints for UX ❑Testing Sprints ❑Lack of Confidence ❑Lack of Trust Symptoms 7
- 8. ❑Definition of Done • Emphasis in Scrum Guide3 • Usable • Evolving o Greenfield Products o Brownfield Products • Aim higher • Retrofit Recommendations 8
- 9. ❑Maturing Engineering Practices4 • Attention to Technical Excellence5 • Artificial Feature Slicing • Non Functional Requirements • Behaviour Driven Development • Test without UI • Screaming Architecture6 Recommendations (cont’d) 9
- 11. Recommendations (cont’d) 11 Simplicity -- the art of maximizing the amount of work not done -- is essential.
- 13. MOHAMMAD NAFEES SHARIF BUTT @mnsbutt