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

1. Don Bolen, PMP, CSM
LS 708
http://www.slideshare.net/dlb1700/
Agile Tools*
for Everyone
*+ practices

2. “PROJECT”
How Projects
become such a

3. “Efficiency and
plannability”

4. Project Lifecycle

5. IT graphic

6. Implementation
Verification
Maintenance
Design
Requirements

7. History of
ADDIE
An Even Briefer

8. http://www.nwlink.com/~donclark/history_isd/addie.html

10. Develop
Implement
Evaluate
Design
Analysis

12. http://www.agilemanifesto.org/

13. 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

14. 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

15. 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

16.  Less defects, better quality
 Increased productivity
 Faster time to market
 Market alignment
 Quicker identification of loser projects
 LEAN
Why Agile?

17. 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

18. 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

19. Which is better?

20. SCRUM

21. Scrum
• A process framework
• Team roles
• Rules
• Timeboxed iterations (SPRINTS)
• Prescribed, limited meetings
https://www.scrum.org/Scrum-Guide

22. http://www.mountaingoatsoftware.com/system/asset/file/17/ScrumLargeLabe
lled.png
Product Owner | Team | Scrum Master

23. Sprint Planning
• Define sprint goal, product backlog
• Team estimates time
• Selects stories for sprint
• Selects time for daily scrum
• Defines “DONE”
iterations

24. Tool #1

25. 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

26. Tool #2

27. Task Board
story to do
in
progress done
Sprint
Goal
unplanned next
burndown

28. http://www.mountaingoatsoftware.com/system/hidden_asset/file/33/LabelledTaskB
oard.jpg

30. http://scrum4kids.blogspot.com/2010/09/using-scrum-for-saturday-
chores.html

31. Which is better?

32. http://joel.inpointform.net/wp-content/uploads/2010/11/burndown132.png
Which is better?

33. Tool #3

34. Measuring via “Burndown”WorkRemaining
Date
Start
End

35. http://www.infoq.com/articles/agile-kanban-boards

36. http://joel.inpointform.net/wp-content/uploads/2010/11/reading-burn-down-chart2.png

37. http://chandoo.org/img/pm/data-burndown-chart.png
http://chandoo.org/wp/2009/07/21/burn-down-
charts/

38. Tool #4

39. “Shippable”
Product
Sprint Review/Retrospective
• Review what/was not completed
• Present “working” increment
• Reflect on what worked/what
didn’t
• Identify improvements

40. Scrum and SAM

41. KANBAN

42. • Visualize the workflow
• Limit Work In Progress (WIP)
• Manage flow
• Process policies must be explicit, DONE is
defined
• Improve collaboratively
Kanban

43. Tool #5

44. backlog doing (3) testing done
FLOW

45. backlog doing (3) testing done
urgent!!

47. http://leankit.com/

48. http://www.nytimes.com/interactive/2011/05/18/business/delta-northwest-merger-
graphic.html?ref=business

49. Tool(s) #6

50. • Kanban board
• WIP limits, not Sprints, daily Scrum standup
• Planning meetings as needed
• Review/Retrospectives
• Cycle time as primary metric
Scrumban

51. Scrumban and SAM…

52. • 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

53. Thank
YouDon Bolen, PMP, CSM
don@dbolen.com
@dbolen
http://www.slideshare.net/dlb1700/