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.

1. MOHAMMAD NAFEES SHARIF BUTT
@mnsbutt
Toolset for Creating a
Potentially Shippable
Product Increment

3. Speaker Bio
❑Mohammad Nafees Sharif Butt
• http://au.linkedin.com/in/mnsbutt
• https://twitter.com/mnsbutt
❑Experience
• 9+ years in SDLC & Project Management
• ~5 years in Agile/Scrum/XP
• Certified Scrum Professions (CSP)
• PMI-ACP & PMP
• CSSLP, TOGAF 9, ITIL v3 Foundation
• OCP-JEE5WCD, SCJP
❑Director IT Services - Waseel ASP Ltd.
❑Founder & Organizer - Riyadh Agile & Scrum
User Group (endorsed by Scrum Alliance)
3

4. Agenda
❑Problem Statement
❑Symptoms
❑Recommendations
❑Questions & Answers
4

5. Problem Statement
❑Market Trend
• Lean Startups
• Disruptive Innovation
• Speakers/Talks today
❑Forces at Work
• Time To Market (TTM)
• Lead Time
• Minimum Viable Product (MVP)
• Minimal Marketable Product (MMP)
5

6. Problem Statement(cont’d)
❑Accrue Technical Debt
❑Technical Debt Classification1
6

7. Problem Statement(cont’d)
❑Design Stamina Hypothesis2
7

8. Symptoms
❑Not being able to demo a feature
❑N+2 Sprints for UX
❑Testing Sprints
❑Lack of Confidence
❑Lack of Trust
8

9. Recommendations
❑Definition of Done
• Emphasis in Scrum Guide3
• Usable
• Evolving
o Greenfield Products
o Brownfield Products
• Aim higher
• Retrofit
9

10. Recommendations (cont’d)
❑Maturing Engineering Practices4
• Attention to Technical Excellence5
• Artificial Feature Slicing
• Non Functional Requirements
• Behaviour Driven Development
• Test without UI
• Screaming Architecture6
10

11. Recommendations (cont’d)
❑Clean Architecture7
11

12. Recommendations (cont’d)
12
Simplicity --
the art of maximizing the
amount of work not
done
-- is essential.

13. Questions & Answers
13

14. Thank You