You think you know agile

  • View
    107

  • Download
    1

Embed Size (px)

DESCRIPTION

Combined slide decks from the presentation at Progressive.net 2011

Text of You think you know agile

  • 1. You think you know agile?
    The where, what and how of agile
    nathan.gloyn@dotnetsolutions.co.uk
    Design Code Release
    nathangloyn
    @NathanGloyn

2. Agenda
You Decide!
3. ROOTS...
4. Roots...
When agile was born
Heavy weight project management processes
Misunderstood requirements
Missed deadlines or death march projects
Inability to change requirements
Applications with lots of defects
Increases the cost
5. Roots...
Scrum first described
1986
DSDM, Adaptive Software Development
Scrum
1995
1996
Extreme Programming (XP), Crystal Clear
1997
Feature Driven Development
2001
Agile Manifesto
2004
Kanban
?
?
6. Roots...
Agile Manifesto
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
7. Roots...
Agile Manifesto 12 Principles
Customer satisfaction by rapid delivery of useful software
Welcome changing requirements, even late in development
Working software is delivered frequently (weeks rather than months)
8. Roots...
Agile Manifesto 12 Principles
Working software is the principal measure of progress
Sustainable development, able to maintain a constant pace
Close, daily co-operation between business people and developers
9. Roots...
Agile Manifesto 12 Principles
Face-to-face conversation is the best form of communication (co-location)
Projects are built around motivated individuals, who should be trusted
Continuous attention to technical excellence and good design
10. Roots...
Agile Manifesto 12 Principles
Simplicity
Self-organizing teams
Regular adaptation to changing circumstances
11. Concepts
12. Concepts
Control
13. Concepts
Communication
14. Concepts
Collaboration
15. Concepts
Cooperation
16. Concepts
Commitment
17. Team
18. Team
The team is:
Critical to success
Not a bunch of individuals
No Heros
Not dependent on any member
Empowered
Trusted
19. Team
Who is in the team?
Team Member
Product Owner
Customer
20. Team
Who is a Team Member?
Developer
Tester
Business Analyst
Team Lead
Architect
Product Owner
21. Team
Do we need a product owner?
Focus on what to deliver
Customer Proxy
Product Manager
Project Manager not a good fit
Not good idea to be a team lead or manager
22. Team
Where does a Scrum Master/Coach fit in?
Guardian of the teams process
Servant/Leader
Helps foster the idea of team
Should never be a team lead or manager
Focused on helping team deliver
23. Team
Do we need a project manager?
Generally no
Responsibilities distributed
Product owner
Coach/Scrum Master
Some projects have to be waterfall
24. Team
Generalist
OR
Specialist?
25. Team
A Self Team
Self Organising
Self Directing
Self Managing
26. Methodologies
27. Methodologies
Currently 3 main stream:
Scrum
XP
Kanban
28. Methodologies: Scrum
29. Methodologies: Scrum
TO DO
WIP
Done
30. Methodologies: XP
31. Methodologies: XP
TO DO
WIP
Done
32. Methodologies: Kanban
Input Queue
In Process
Done
Available capacity
33. Methodologies: Kanban
TO DO
WIP (2)
Done
34. Methodologies
Commonalities:
Visibility/Transparency
User stories
Pull Based
Definition of done
Sustainable pace
Continuous Improvement
35. Methodologies: Helicopter View
Scrum
XP
Kanban
Plan release
Plan iteration
Work through items
Release when Done, Done
Iteration Retrospective
Release Retrospective
Plan sprint
Work on items in sprint
Review
Retrospective
Input queue
Pull item to work
Work until meets done criteria
Repeat
36. Methodologies: Meetings
Scrum
XP
Kanban
Release Planning
Iteration Planning
Standup
Iteration Retrospective
Release Retrospective
Daily Stand-up
Sprint Review
Sprint Retrospective
Sprint Planning
Backlog grooming
None
37. Methodologies: Roles
Scrum
XP
Kanban
Customer
Coach
Team
Customer
Product Owner
Scrum Master
Development Team
What ever you
currently have
38. Methodologies: Artifacts
Scrum
XP
Kanban
Board
Charts
More charts!
Card Board
Backlog
Definition of Done
Burndown
Board
What ever reports you wish to create
39. Methodologies: Metrics
Scrum
XP
Kanban
Lead time
Cycle time
Throughput performance
Due date completion
etc
Velocity
Velocity
40. Methodologies:Continuous Improvement
Scrum
XP
Kanban
Kaizen culture
Kaizen blitz
Slack
Inspect & Adapt
Sprint retrospective
Iteration retrospectives
Release retrospective
41. Methodologies: Differentiators
Scrum
Estimation
Commitment Forecasting
Iterations
Team decide what to pull into an iteration
42. Methodologies: Differentiators
XP
Short Iterations
Done, Done
Rules
5 Values
14 Principles
24 Practices
43. Methodologies: Differentiators
Kanban
Flow
Cadence
Policies
Classes of Service
44. Methodologies: Comparison
45. Lean
46. Lean
What is Lean?
From manufacturing
Toyota Production System (TPS)
Just In Time (JIT) production
Kanban card
Kaizen
Poppendicks
Lean Software Development: An Agile Toolkit (2003)
David J Anderson
Kanban - Successful Evolutionary Change for your Technology Business
47. Lean: Principles
Eliminate Waste
48. Lean: Principles
Build Quality In
49. Lean: Principles
Create Knowledge
50. Lean: Principles
Defer Commitment
51. Lean: Principles
Deliver Fast
52. Lean: Principles
Respect People
53. Lean: Principles
Optimise the whole
54. Whats next?
55. Whats next?
ScrumBan
Lean Startup
The rise of lean
Death of the Iron triangle?
56. Whats next: Scrumban
Mixture of Kanban & Scrum
Workflow of Kanban
Backlog column for iteration
Ready column for higher priority work
Meetings of Scrum
57. Whats next: The rise of lean
The next best thing?
Beware marketing speak
Can help whatever process you are using
Kanban
58. Whats Next: Lean Startup
new methodology
Focused on getting product out there
More a business methodology
Kanban great fit
Beware comparisons to agile
59. Whats Next: Lean Startup
60. Whats next: Death of the Iron triangle?
Cost exists anyway
Quality should be a given
Scope flexible
Possibly in enterprises
Unlikely with external clients
61. Sum up
62. Summary
Lots of ideas
Pull in what works
Throw away what doesnt
Create your own process
Stay true to principles
nathan.gloyn@dotnetsolutions.co.uk
Design Code Release
nathangloyn
@NathanGloyn