why' is important than 'how' : presented by gaurav rastogi
TRANSCRIPT
• ‘Why’ is important Than ‘How’• What Successful companies do• Figure your company ‘WHY’• Agile Survey Facts
Speaker : Gaurav Rastogi Organization : Fidelity Investments Ltd.
Topic : ‘WHY’ is Important Than ‘HOW’
Agenda
WHY is important than HOW
1
whyhow
3
4
5
Why Apple is so innovative ?
6
If Apple were like everyone else, A marketing message from them might sound like this: "We make great computers. They're beautifully designed, simple to use and user friendly. Want to buy one?"
The Golden Circle !!!
6
Everything we do, we believe in challenging the status quo.We believe in thinking differently. The way we challenge the status quo is by making our products beautifully designed, simple to use and user friendly. We just happen to make great computers. Want to buy one?"
Source: TED.com : Simon Sinek
ABCD of Transformation
A - Analyze
B - Believe
C - Commit
D - Deliver
WHY do AGILE Transformation for companies do work and for some it doesn't?
2
Here is what I found out!
11
AGILE
Collaboration Transparency Automation
IT/Business alignment
Distributed teams
Faster Time to Market
Productivity
Risk Management
Simplify Delivery
Quality
Focal Point
Business Value
We Want everything
7
TEAM WORK
Cross-cutting skillsIncludes all rolesTeam Size (8-12)Co-location / working togetherSelf-organized
Specialized skillsPartial role composition
Large teamsReliance on SMEs
PLANNING
Well-defined sprint backlogCombined release planningTech team influence s scopeSprint duration (2-4 weeks)Team knows their velocityWell-defined acceptance criteriaCollaborative estimation
Switching prioritiesRelease planning in silo
Pre-defined scope & deadlinesProductivity not knownAbsence of used cases
REQUIREMENTSEffective grooming sessionsNFRs defined early & clearlyPrioritized Product BacklogWell-defined acceptance criteria
Ineffective or no groomingNFRs not clearly defined
Incomplete requirementsUnhealthy Pipeline of requirements
Absence of used cases
COMMUNICATIONEffective stand-up meetingsHigh bandwidth communicationInformal communication
No AccountabilityInfrequent or low b/w comm.
Formal communication
TECHNICAL PRACTICES
Iterative DesignContinuous IntegrationTDD approachTech Debt reductionPair programming
Upfront designLow quality of code
Lack of pair programmingLack of Tech Debt visibility
Lack of CI & Automated Tests
QUALITY
Automated TestingQA involved from beginningBugs fixed during sprintIT, UAT, Perf TestingWell-defined criteria for DONEPQM Tracking
Mostly manual testingBugs caught late in development
Lack of variety in testingVague used cases
Lack of independent testingNo PQM tracking
Why? Heat map Model
13
Why
Why
Why
Why
Why
More ImportantLess Important
Less ImprovementRequired
More ImprovementRequired
Why?
12
Facts
8
Why is missing
Why is missing
Sourcewww.versionone.com
FACTS – Source 8th Annual State of Agile Survey
10
Sourcewww.versionone.com
FACTS – Source 8th Annual State of Agile Survey
9
FACTS – Source 8th Annual State of Agile Survey
Sourcewww.versionone.com
11
