Scrum jan 22nd - manoj vadakan - conscires agile practices
-
Upload
conscires-agile-practices -
Category
Business
-
view
292 -
download
0
Transcript of Scrum jan 22nd - manoj vadakan - conscires agile practices
Going Agile? What is in it for me?
M A N O J V A D A K K A N
Manoj [email protected]
H O S T E D B YBachan AnandConscires Agile [email protected]
Conscires Agile Practices
Who we are ::
Enabler of Agile & Scrum adoption for your organization
Agile Adoption Assessment, Training & Coaching
What we do :: Agile & Scrum Coaching – http://agile.conscires.com/services/
Agile & Scrum Trainings - http://bit.ly/allTrainings
Boston,MA
Irvine,CA
San Diego,CA
Phoenix, AZ
Your experience with Agile
I don’t know what Agile is
Understand the values of Agile
Started using Agile but have Challenges
I am sailing smooth on my Agile boat
3
Agenda
Why Agile?
What is In In It For Me?
What is Scrum?
4
About your facilitator
5
Certifications6
Organizations consulted with7
Currently with8
Previous Speaking Engagements9
Iterative Vs. Agile
10
Homework Problem11
http://alistair.cockburn.us/Are+iterations+hazardous+to+your+project%3F
The Homework ProblemIterative vs. Agile
A School homework assignment
Read 10 books answer 20 questions
Submit answers by Following Monday (1 week to complete the assignment)
12
http://alistair.cockburn.us/Are+iterations+hazardous+to+your+project%3F
http://www.scrumalliance.org/articles/134-iterative-vs-agile
Homework Problem13
Homework Problem14
Homework ProblemThe plan
Read two book every day (M-F)
Spend Saturday to answer questions
Submit answers on Monday
15
0
2
4
6
8
10
12
Monday Tuesday Wednesday Thursday Friday Saturday
# of Books to Read
# of Questions
Homework ProblemWhat Really Happened
Student read books as per plan.
Status on Friday - Green
Started looking at questions on Saturday to realize that books need to be read again for the most part
Status on Saturday - Red
16
0
2
4
6
8
10
12
# of Books to Read
# of Questions
What is the point?
How the student should have measured his progress?
Number of Books read?
Number of Questions answered?
How do you measure progress in your projects?
17
18
Agile
Agile Manifestowww.agilemanifesto.org
19
Agile Manifestowww.agilemanifesto.org
Individuals & interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
20
That is, while there is value in the items on the right,
we value the items on the left more.
Responding to Change
21
Working Software
22
Working Software
Track Record
23
The Plan Driven development: The Plan
24
The Plan Driven developmentThe Plan
25
The Plan Driven development: The Plan
26
The Plan Driven development: The Plan
27
The Plan Driven development: The Plan
28
The Plan Driven development: The Plan
29
The Plan Driven developmentOct Target date
30
Reality?
31
The Plan Driven development: Reality
32
The Plan Driven development: Reality
33
The Plan Driven development: Reality
34
The Plan Driven development: Reality
35
The Plan Driven developmentNew Date
36
The Plan Driven developmentsystem testing
37
bugs38
The Plan Driven developmentProduction Release
39
The Plan Driven developmentProduction Release
delivered in March
40
The Plan Driven developmentProduction Release
5 Months late
41
The Plan Driven development: Prod. Release
no new business value for 15 months
42
Trust?
43
How do we build the Trust?
44
What if we deliver
working Software
with business value from the first week/month
45
What if we deliver
working Software
Frequently
46
Agile Manifestowww.agilemanifesto.org
Individuals & interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
47
That is, while there is value in the items on the right,
we value the items on the left more.
Agile is not an Excuse for
We don’t need to plan anything
We don’t need to document anything
48
Lazy Agile
49
50
Why Agile?
Why Agile?
We may have better process efficiency than we ever had before.
How do we improve now?
Is the budget/schedule getting shorter?
How about value delivered & Time to Market?
Business Value
Is prioritization an afterthought?
When/who prioritize features?
Late? may be when we are really sure we can not do it all within the time?
Applying the Pareto Principle
Reasons for Project Failure
54
Lack of User Input 13%
Incomplete Requirements & Specifications 12%
Changing Requirements & Specifications 11%
Lack of Executive Support 8%
Technology Incompetence 7%
Lack of Resources 6%
Unrealistic Expectations 6%
Unclear Objectives 5%
Unrealistic Timeframes 4%
New technology 4%
Other 23%
Extracted from CHAOS Report : The Standish Group 1995
55
User Involvements 16%
Executive Management Support 14%
Clear statements of Requirements 13%
Proper Planning 10%
Realistic Expectations 8%
Smaller Project Milestones 8%
Competent Staff 7%
Ownership 5%
Clear Vision and Objectives 3%
Hardworking, Focused Staff 2%
Other 14%
Extracted from CHAOS Report : The Standish Group 1995
Reasons for Project Success
What is in it for me?
As a customer , I want to be able to Go to market faster Faster return on investment Opportunity to provide feedback early
As a Project Manager/Leadership, I want To measure progress in terms of real progress made on product . Better engaged and accountable team
As a team member, I want A sustainable pace Satisfaction of quality product delivered Clear Priority and less interruption during development
56
57
Scrum A quick Introduction Scrum
Scrum
A process framework for managing product development
Not a methodology
58
Sprint
Sprint
Sprint
Sprint
Sprint
Production
Release
Product Owner with
Stakeholders/PMO
Product Owner with
Stakeholders/PMO
Product Backlog
Feedback from Sprint
Reviews
Feedback from Releases
Sprint = Iteration
Discovery Period
During the Discovery Period, the product team identify the features, prioritize the features, and identify a
roadmap for the product. The roadmap will identify the release milestones into production and the features
contained in each releases at a high-level.
Each Sprint deliver (for a subset of Product Backlog) running tested features potentially shippable that the team
can demonstrate to the customer to get feedback
Multiple sprints
usually build up a
release
Agile Product Development
Product Owner with
Stakeholders/PMO
With the help of the Product Owner, the team selects a set of features from the top of the prioritized product
backlog.
Team Spends 2 to 4 hours on the first day of the sprint to break down the features to detail tasks (technical,
testing, documentation, etc) and estimate hours needed to complete them.
Within the sprint the team deliver Running Tested Features along with all the documentation for the selected
features.
The product from the sprint is demonstrated to the customer to get feedback.
Sprints are of the consistent, fixed length for a project, usually 1 week to 4 weeks.
Agile Product Development: Sprints
Product
Backlog
Sprint
Backlog
Sprint
Task List
Sprint
Demo
The team
creates working
software for the
features
selected for the
Sprint including
all the
necessary
Documentation Sprint
Potentially
shippable
product
Initial Analysis for
the sprint backlog
Acceptance
Criteria
Defined for Sprint
Scrum61
• Roles
• Product owner
• Scrum Master
• Team
• Ceremonies
• Daily Scrum
• Sprint Planning
• Sprint Review-Demo
• Retrospective
• Artifacts
• Product Backlog
• Sprint Backlog
• Planning
• Release plan
• Progress Tracking
• Velocity
• Burn down Chart
What is in it for me?
As a customer , I want to be able to Go to market faster
Faster return on investment
Opportunity to provide feedback early
As a Project Manager/Leadership, I want To measure progress in terms of real progress made on product .
Better engaged and accountable team
As a team member, I want A sustainable pace
Satisfaction of quality product delivered
Clear Priority and less interruption during development
62
Upcoming Trainings in Boston,MA
“What is Scrum” by Manoj Vadakan on Feb 19th 2011
Certified ScrumMaster Training by Alan Cyment on April 7th – 8th 2011
20% discount with code Webinar0122
Contact Bachan Anand
W : http://agile.conscires.com
P : 949-232-8900
Thank you !
Work is GOOD !http://work-is-good.com