Don Bolen, PMP, CSM
LS 708
http://www.slideshare.net/dlb1700/
Agile Tools*
for Everyone
*+ practices
“PROJECT”
How Projects
become such a
“Efficiency and
plannability”
Project Lifecycle
IT graphic
Implementation
Verification
Maintenance
Design
Requirements
History of
ADDIE
An Even Briefer
http://www.nwlink.com/~donclark/history_isd/addie.html
Develop
Implement
Evaluate
Design
Analysis
http://www.agilemanifesto.org/
The Principles
- Customer satisfaction by rapid delivery of useful software
- Welcome changing requirements, even late in ...
The Principles
- Customer satisfaction by rapid delivery of useful software
- Welcome changing requirements, even late in ...
Traditional
Plan what you expect
to happen
Enforce the plan
Large, in-charge PM
Directive, top down
Use change control
Agi...
 Less defects, better quality
 Increased productivity
 Faster time to market
 Market alignment
 Quicker identificatio...
Agile “flavors”
 Scrum
 Kanban
 Lean Agile
 Extreme Programming (XP)
 Unified Processes (RUP, AUP, OP)
 Features Dri...
Agile “flavors”
 Scrum
 Kanban
 Lean Agile
 Extreme Programming (XP)
 Unified Processes (RUP, AUP, OP)
 Features Dri...
Which is better?
SCRUM
Scrum
• A process framework
• Team roles
• Rules
• Timeboxed iterations (SPRINTS)
• Prescribed, limited meetings
https://w...
http://www.mountaingoatsoftware.com/system/asset/file/17/ScrumLargeLabe
lled.png
Product Owner | Team | Scrum Master
Sprint Planning
• Define sprint goal, product backlog
• Team estimates time
• Selects stories for sprint
• Selects time fo...
Tool #1
Daily Scrum Meeting
• Ask
What did you yesterday?
What will you do today?
What obstacles do you have?
• 15 minutes
• In fr...
Tool #2
Task Board
story to do
in
progress done
Sprint
Goal
unplanned next
burndown
http://www.mountaingoatsoftware.com/system/hidden_asset/file/33/LabelledTaskB
oard.jpg
http://scrum4kids.blogspot.com/2010/09/using-scrum-for-saturday-
chores.html
Which is better?
http://joel.inpointform.net/wp-content/uploads/2010/11/burndown132.png
Which is better?
Tool #3
Measuring via “Burndown”WorkRemaining
Date
Start
End
http://www.infoq.com/articles/agile-kanban-boards
http://joel.inpointform.net/wp-content/uploads/2010/11/reading-burn-down-chart2.png
http://chandoo.org/img/pm/data-burndown-chart.png
http://chandoo.org/wp/2009/07/21/burn-down-
charts/
Tool #4
“Shippable”
Product
Sprint Review/Retrospective
• Review what/was not completed
• Present “working” increment
• Reflect on...
Scrum and SAM
KANBAN
• Visualize the workflow
• Limit Work In Progress (WIP)
• Manage flow
• Process policies must be explicit, DONE is
defined...
Tool #5
backlog doing (3) testing done
FLOW
backlog doing (3) testing done
urgent!!
http://leankit.com/
http://www.nytimes.com/interactive/2011/05/18/business/delta-northwest-merger-
graphic.html?ref=business
Tool(s) #6
• Kanban board
• WIP limits, not Sprints, daily Scrum standup
• Planning meetings as needed
• Review/Retrospectives
• Cycl...
Scrumban and SAM…
• Limit WIP
• Commit to frequent releases
• Pull the work
• Be transparent (Task/Kanban board)
• Collaborate
• Do what wor...
Thank
YouDon Bolen, PMP, CSM
don@dbolen.com
@dbolen
http://www.slideshare.net/dlb1700/
LS 708 Agile Tools for Everyone
LS 708 Agile Tools for Everyone
LS 708 Agile Tools for Everyone
LS 708 Agile Tools for Everyone
Upcoming SlideShare
Loading in...5
×

LS 708 Agile Tools for Everyone

349

Published on

Presentation provides agile tools and practices that workplace learning professionals can use with projects. Deck built for Learning Solutions 2014 with presenter notes

Published in: Business
1 Comment
0 Likes
Statistics
Notes
  • Be the first to like this

No Downloads
Views
Total Views
349
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
8
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

LS 708 Agile Tools for Everyone

  1. 1. Don Bolen, PMP, CSM LS 708 http://www.slideshare.net/dlb1700/ Agile Tools* for Everyone *+ practices
  2. 2. “PROJECT” How Projects become such a
  3. 3. “Efficiency and plannability”
  4. 4. Project Lifecycle
  5. 5. IT graphic
  6. 6. Implementation Verification Maintenance Design Requirements
  7. 7. History of ADDIE An Even Briefer
  8. 8. http://www.nwlink.com/~donclark/history_isd/addie.html
  9. 9. Develop Implement Evaluate Design Analysis
  10. 10. http://www.agilemanifesto.org/
  11. 11. The 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) - 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 - 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 - Simplicity - Self-organizing teams - Regular adaptation to changing circumstance
  12. 12. The 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) - 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 - 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 - Simplicity - Self-organizing teams - Regular adaptation to changing circumstance
  13. 13. Traditional Plan what you expect to happen Enforce the plan Large, in-charge PM Directive, top down Use change control Agile Plan what you expect by iteration Control is through adaption/ inspection Use Agile proactively to manage change Contrasting Approaches
  14. 14.  Less defects, better quality  Increased productivity  Faster time to market  Market alignment  Quicker identification of loser projects  LEAN Why Agile?
  15. 15. Agile “flavors”  Scrum  Kanban  Lean Agile  Extreme Programming (XP)  Unified Processes (RUP, AUP, OP)  Features Driven Development  Crystal  Test Driven Development The State of Scrum 2013, Scrum Alliance
  16. 16. Agile “flavors”  Scrum  Kanban  Lean Agile  Extreme Programming (XP)  Unified Processes (RUP, AUP, OP)  Features Driven Development  Crystal  Test Driven Development OUR FOCUS The State of Scrum 2013, Scrum Alliance
  17. 17. Which is better?
  18. 18. SCRUM
  19. 19. Scrum • A process framework • Team roles • Rules • Timeboxed iterations (SPRINTS) • Prescribed, limited meetings https://www.scrum.org/Scrum-Guide
  20. 20. http://www.mountaingoatsoftware.com/system/asset/file/17/ScrumLargeLabe lled.png Product Owner | Team | Scrum Master
  21. 21. Sprint Planning • Define sprint goal, product backlog • Team estimates time • Selects stories for sprint • Selects time for daily scrum • Defines “DONE” iterations
  22. 22. Tool #1
  23. 23. Daily Scrum Meeting • Ask What did you yesterday? What will you do today? What obstacles do you have? • 15 minutes • In front of the Task Board
  24. 24. Tool #2
  25. 25. Task Board story to do in progress done Sprint Goal unplanned next burndown
  26. 26. http://www.mountaingoatsoftware.com/system/hidden_asset/file/33/LabelledTaskB oard.jpg
  27. 27. http://scrum4kids.blogspot.com/2010/09/using-scrum-for-saturday- chores.html
  28. 28. Which is better?
  29. 29. http://joel.inpointform.net/wp-content/uploads/2010/11/burndown132.png Which is better?
  30. 30. Tool #3
  31. 31. Measuring via “Burndown”WorkRemaining Date Start End
  32. 32. http://www.infoq.com/articles/agile-kanban-boards
  33. 33. http://joel.inpointform.net/wp-content/uploads/2010/11/reading-burn-down-chart2.png
  34. 34. http://chandoo.org/img/pm/data-burndown-chart.png http://chandoo.org/wp/2009/07/21/burn-down- charts/
  35. 35. Tool #4
  36. 36. “Shippable” Product Sprint Review/Retrospective • Review what/was not completed • Present “working” increment • Reflect on what worked/what didn’t • Identify improvements
  37. 37. Scrum and SAM
  38. 38. KANBAN
  39. 39. • Visualize the workflow • Limit Work In Progress (WIP) • Manage flow • Process policies must be explicit, DONE is defined • Improve collaboratively Kanban
  40. 40. Tool #5
  41. 41. backlog doing (3) testing done FLOW
  42. 42. backlog doing (3) testing done urgent!!
  43. 43. http://leankit.com/
  44. 44. http://www.nytimes.com/interactive/2011/05/18/business/delta-northwest-merger- graphic.html?ref=business
  45. 45. Tool(s) #6
  46. 46. • Kanban board • WIP limits, not Sprints, daily Scrum standup • Planning meetings as needed • Review/Retrospectives • Cycle time as primary metric Scrumban
  47. 47. Scrumban and SAM…
  48. 48. • Limit WIP • Commit to frequent releases • Pull the work • Be transparent (Task/Kanban board) • Collaborate • Do what works / continually improve • Talk to your IT group for insights • Be Agile Keys to success
  49. 49. Thank YouDon Bolen, PMP, CSM don@dbolen.com @dbolen http://www.slideshare.net/dlb1700/
  1. ¿Le ha llamado la atención una diapositiva en particular?

    Recortar diapositivas es una manera útil de recopilar información importante para consultarla más tarde.

×