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. AGILE MEAGILE ME
MOHAMMAD NAFEES SHARIF BUTT
@mnsbutt
Toolset for Creating a
Potentially Shippable
Product Increment
1

2. AGILE MEAGILE ME
2
gold sponsor
silver sponsor
bronze sponsor
media partner

3. AGILE ME
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. AGILE ME
Agenda
 Problem Statement
 Symptoms
 Recommendations
 Questions & Answers
4

5. AGILE ME
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. AGILE ME
Problem Statement(cont’d)
 Accrue Technical Debt
 Technical Debt Classification1
61 Technical Debt Quadrant by Martin Fowler, retrieved from http://martinfowler.com/bliki/TechnicalDebtQuadrant.html

7. AGILE ME
Problem Statement(cont’d)
 Design Stamina Hypothesis2
72 Design Stamina Hypothesis by Martin Fowler, retrieved from http://martinfowler.com/bliki/DesignStaminaHypothesis.html
t1 t2

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

9. AGILE ME
Recommendations
 Definition of Done
• Emphasis in Scrum Guide3
• Usable
• Evolving
o Greenfield Products
o Brownfield Products
• Aim higher
• Retrofit
93 The official Scrum Guide by Jeff Sutherland & Ken Schwaber, retrieved from http://www.scrumguides.org/

10. AGILE ME
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
4 Principles behind the Agile Manifesto, retrieved from http://agilemanifesto.org/principles.html
5 The Land that Scrum Forgot by Robert C. Martin at Norwegian Developers Conference 2011, retrieved from
https://www.youtube.com/watch?v=hG4LH6P8Syk
6 Architecture the Lost Years by Robert C. Martin at Ruby Midwest 2011 gathering , retrieved from https://www.youtube.com/watch?v=WpkDN78P884

11. AGILE ME
Recommendations (cont’d)
 Clean Architecture7
117 The Clean Architecture by Robert C. Martin, retrieved from http://blog.8thlight.com/uncle-bob/2012/08/13/the-clean-architecture.html

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

13. AGILE ME
Questions & Answers
13

14. AGILE MEAGILE ME
Thank You
14