Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Don Bolen, PMP, CSM
25 FEB
http://www.slideshare.net/dlb1700/
A Brief

History of
PROJECTS
http://static2.wikia.nocookie.net/__cb201106290140
61/althistory/images/5/5b/ICBM.png
How Projects
become such a

“PROJECT?”
“Efficiency and
plannability”
Project Lifecycle
Initiating
• Develop Project
Charter
• Identify
Stakeholders

Planning
• Develop PM Plan
• Collect
Requi...
IT graphic
Requirements

Design

Implementation

Verification

Maintenance
An Even Briefer

History of

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

Design

Develop

Implement

Evaluate
The Manifesto
“We are uncovering better ways of developing software by
doing it and helping others do it. Through this wor...
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 ...
Contrasting Approaches
Traditional
Plan what you expect to
happen
Enforce the plan
Large, in-charge PM
Directive, top down...
Why Agile?
• Less defects, better quality
• Increased productivity
• Faster time to market
• Market alignment
• Quicker id...
Which is better?
SCRUM
Scrum
•
•
•
•
•

A process framework
Team roles
Rules
Timeboxed iterations (SPRINTS)
Prescribed, limited meetings

https:/...
Product Owner | Team | Scrum Master

http://www.mountaingoatsoftware.com/system/asset/file/17/ScrumLargeLabe
lled.png
Sprint Planning
• Define sprint goal, product backlog
• Team estimates time

• Selects stories for sprint
• Selects time f...
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
burndown

unplanned

next
http://scrum4kids.blogspot.com/2010/09/using-scrum-for-saturdaychores.html
Which is better?
Which is better?

http://joel.inpointform.net/wp-content/uploads/2010/11/burndown132.png
Tool #3
Measuring via “Burndown”
Work Remaining

Start

End
Date
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
Tool #4
Sprint Review/Retrospective
• Review what/was not completed
• Present “working” increment
“Shippable”
• Reflect on what wo...
Scrum and SAM…
KANBAN
Kanban
• Visualize the workflow

• Limit Work In Progress (WIP)
• Manage flow
• Process policies must be explicit, DONE is...
Tool #5
backlog

doing (3)

testing

FLOW

done
backlog

urgent!!

doing (3)

testing

done
http://leankit.com/
http://www.nytimes.com/interactive/2011/05/18/business/delta-northwest-mergergraphic.html?ref=business
Tool(s) #6
Kanban to Scrumban
Scrumban
• Kanban board
•

WIP limits, not Sprints, daily Scrum standup

• Planning meetings as needed

• Review/Retrospec...
Keys to success
• Limit WIP
• Commit to frequent releases
• Pull the work
• Be transparent (Task/Kanban board)

• Collabor...
Thank
You

Don Bolen, PMP, CSM
don@dbolen.com
@dbolen
Agile tools for everyone (slideshare)
Agile tools for everyone (slideshare)
Agile tools for everyone (slideshare)
Agile tools for everyone (slideshare)
Agile tools for everyone (slideshare)
Agile tools for everyone (slideshare)
Agile tools for everyone (slideshare)
Upcoming SlideShare
Loading in …5
×

Agile tools for everyone (slideshare)

831 views

Published on

Iteration 1 of presentation 2/25 for Learning technology SIG, Greater Atlanta ASTD.

Published in: Business
  • Be the first to comment

  • Be the first to like this

Agile tools for everyone (slideshare)

  1. 1. Don Bolen, PMP, CSM 25 FEB http://www.slideshare.net/dlb1700/
  2. 2. A Brief History of PROJECTS
  3. 3. http://static2.wikia.nocookie.net/__cb201106290140 61/althistory/images/5/5b/ICBM.png
  4. 4. How Projects become such a “PROJECT?”
  5. 5. “Efficiency and plannability”
  6. 6. Project Lifecycle Initiating • Develop Project Charter • Identify Stakeholders Planning • Develop PM Plan • Collect Requirements • Define Scope • Create WBS • Define, Sequence Activities • Estimate Activity Resources, Durations • Estimate Costs • Determine Budget • Quality • Develop HR Plan • Plan Communications • Risk Management • Identify Risks • Risk Analysis, Responses • Plan Procurements Executing • Manage Project Execution • Perform QA • Acquire, Develop, Manage Team • Distribute Information • Manage Stakeholder Expectations • Conduct Procurements Monitoring & Controlling • Monitor, Control Project Work • Change Control • Verify, Control Scope • Control Schedule • Control Costs • Perform QC • Report Performance • Monitor, Control Risks • Administer Procurements Closing • Close Project • Close Procurements
  7. 7. IT graphic
  8. 8. Requirements Design Implementation Verification Maintenance
  9. 9. An Even Briefer History of ADDIE
  10. 10. http://www.nwlink.com/~donclark/history_isd/addie.html
  11. 11. Analysis Design Develop Implement Evaluate
  12. 12. The Manifesto “We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: - 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.” http://www.agilemanifesto.org/
  13. 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. 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. 15. Contrasting Approaches 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
  16. 16. Why Agile? • Less defects, better quality • Increased productivity • Faster time to market • Market alignment • Quicker identification of loser projects • LEAN
  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. Product Owner | Team | Scrum Master http://www.mountaingoatsoftware.com/system/asset/file/17/ScrumLargeLabe lled.png
  21. 21. Sprint Planning • Define sprint goal, product backlog • Team estimates time • Selects stories for sprint • Selects time for daily scrum • Defines “DONE”
  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 burndown unplanned next
  26. 26. http://scrum4kids.blogspot.com/2010/09/using-scrum-for-saturdaychores.html
  27. 27. Which is better?
  28. 28. Which is better? http://joel.inpointform.net/wp-content/uploads/2010/11/burndown132.png
  29. 29. Tool #3
  30. 30. Measuring via “Burndown” Work Remaining Start End Date
  31. 31. http://www.infoq.com/articles/agile-kanban-boards
  32. 32. http://joel.inpointform.net/wp-content/uploads/2010/11/reading-burn-down-chart2.png
  33. 33. http://chandoo.org/img/pm/data-burndown-chart.png
  34. 34. Tool #4
  35. 35. Sprint Review/Retrospective • Review what/was not completed • Present “working” increment “Shippable” • Reflect on what worked/what Product didn’t • Identify improvements
  36. 36. Scrum and SAM…
  37. 37. KANBAN
  38. 38. Kanban • Visualize the workflow • Limit Work In Progress (WIP) • Manage flow • Process policies must be explicit, DONE is defined • Improve collaboratively
  39. 39. Tool #5
  40. 40. backlog doing (3) testing FLOW done
  41. 41. backlog urgent!! doing (3) testing done
  42. 42. http://leankit.com/
  43. 43. http://www.nytimes.com/interactive/2011/05/18/business/delta-northwest-mergergraphic.html?ref=business
  44. 44. Tool(s) #6
  45. 45. Kanban to Scrumban
  46. 46. Scrumban • Kanban board • WIP limits, not Sprints, daily Scrum standup • Planning meetings as needed • Review/Retrospectives • Cycle time as primary metric
  47. 47. Keys to success • Limit WIP • Commit to frequent releases • Pull the work • Be transparent (Task/Kanban board) • Collaborate • Do what works • Be AGILE
  48. 48. Thank You Don Bolen, PMP, CSM don@dbolen.com @dbolen

×