LS 708 Agile Tools for Everyone
Upcoming SlideShare
Loading in...5
×
 

LS 708 Agile Tools for Everyone

on

  • 235 views

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

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

Statistics

Views

Total Views
235
Views on SlideShare
235
Embed Views
0

Actions

Likes
0
Downloads
1
Comments
1

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    LS 708 Agile Tools for Everyone LS 708 Agile Tools for Everyone Presentation Transcript

    • 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 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
    • 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
    • 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
    •  Less defects, better quality  Increased productivity  Faster time to market  Market alignment  Quicker identification of loser projects  LEAN Why Agile?
    • 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
    • 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
    • Which is better?
    • SCRUM
    • Scrum • A process framework • Team roles • Rules • Timeboxed iterations (SPRINTS) • Prescribed, limited meetings https://www.scrum.org/Scrum-Guide
    • 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 for daily scrum • Defines “DONE” iterations
    • Tool #1
    • 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
    • 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 what worked/what didn’t • Identify improvements
    • Scrum and SAM
    • KANBAN
    • • Visualize the workflow • Limit Work In Progress (WIP) • Manage flow • Process policies must be explicit, DONE is defined • Improve collaboratively Kanban
    • 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 • Cycle time as primary metric Scrumban
    • Scrumban and SAM…
    • • 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
    • Thank YouDon Bolen, PMP, CSM don@dbolen.com @dbolen http://www.slideshare.net/dlb1700/