Ls14 798 bolen_b

702 views

Published on

Resources and references for LS 708 Agile Tools for Everyone Presentation

Published in: Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
702
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Ls14 798 bolen_b

  1. 1. Agile Tools for Everyone: Resources The Agile Manifesto (http://www.agilemanifesto.org/) and the Twelve Principles of Agile Software (http://www.agilemanifesto.org/principles.html) Mike’s Blog provides insights and practical advice to those new to Agile and Scrum. http://www.mountaingoatsoftware.com/blog The Scrum Alliance - http://www.scrumalliance.org/ Scrum The Scrum Guide provides the rules and serves as the official “Scrum Body of Knowledge” https://www.scrum.org/Scrum-Guide Mike Cohn of Mountain Goat Software provides a library of resources about Agile including this introduction to Scrum under a Creative Commons Attribution license. http://www.mountaingoatsoftware.com/presentations In Agile software development, user stories are crafted with straightforward, everyday language that captures customer expectations and requirements. User stories typically use a persona exercise as: As a < user role >, I want < goal > so that < value >. Examples: As a learner, I want my eLearning courses to have open navigation so that I can freely move through the course. As a manager, I want my employees to be able to test out of content that they already know so that the training is efficient and they’re back to work as soon as possible.
  2. 2. A backlog is a list of the prioritized stories. Estimating is a challenge for software projects. Agile teams use the concept of story points to determine the relative size of the story. Story points represent the relative size based upon effort, complexity and risk. See http://www.agilenutshell.com/estimation_and_planning and this video http://www.agilenutshell.com/episodes/3-estimation. Planning Poker is an agile estimating and planning technique that is consensus based. http://www.mountaingoatsoftware.com/agile/planning-poker Planning Poker is also available in an online version. http://www.planningpoker.com/ Tool #1 Daily Scrum The Daily Scrum is held on the same time and place each working day.   Each team member states o What did you yesterday? o What will you do today? o What obstacles do you have? Limited to 15 minutes Only team members participate in the Daily Scrum For remote teams, conduct the Daily Scrum via conference.
  3. 3. Tool #2 The Task Board with Story Points http://www.mountaingoatsoftware.com/system/asset/file/29/MockedTaskBoard.jpg
  4. 4. Task Board Tips       Keep it simple OK to evolve and improve your task board Post definition of DONE The team owns the board Assign responsibilities to team members Capture unplanned work on the board Scrum is not just for software development. Scrum can also be used to organize family chores. http://scrumforkids.com/ Schools are also using Scrum http://scrum.jeffsutherland.com/2012/04/scrum-future-for-education.html and http://tracks.roojoom.com/u/shirly-ronen-harel,60/scrum-in-school-eduscrum-2,2022#/introduction
  5. 5. Tool #3 Burndown Charts A burndown chart compares actual to plan. Links to two approaches in Excel This is the simpler approach in creating the burndown: http://chandoo.org/wp/2009/07/21/burn-down-charts/ This Excel file is more complex: http://joel.inpointform.net/software-development/burn-down-charts-tutorialsimple-agile-project-tracking/
  6. 6. Tool #4 Sprint Review/Retrospective During this Review, the Scrum team shows what they accomplished during the sprint; typically this is a demo of the new features and is informal. Think of the Retrospective as a lessons learned session where the team will invoke the lessons with the next sprint. One approach is to ask what should we:    Start doing Stop doing Continue doing
  7. 7. Tool #5 Kanban Board Sample: To Do Doing Done Additional columns can be added as required; ex, Approvals Remember to move from one column must be explicit. You must define what is required to move from Doing to Done
  8. 8. References David J Anderson, Kanban, 2010 Jim Benson & Tonianne DeMaria Barry, Personal Kanban: Mapping Work | 
 Navigating Life, 2011 Henrick Kniberg & Mattias Skarin, Kanban and Scrum, Making the most of both, 2010 Project Management Body of Knowledge, 5th Edition, 2013 Ken Schwaber, Agile Project Management with Scrum, 2004 Ken Schwaber & Jeff Sutherland, Scrum Guide July 2013 https://www.scrum.org/Scrum-Guide Michele Sliger & Stacia Brokerick, The Software Project Manager’s Bridge to Agility, 2008 Sylvain Lenfle and Christoph Loch, “Lost Roots: How Project Management Came to Emphasize Control Over Flexibility and Novelty” crg.polytechnique.fr/fichiers/crg/publications/pdf/2010-10-31-1638.pdf Don Bolen don@dbolen.com

×