Agile letvægts projektstyring med Google PROSA, 31/ Thomas Blomseth, BestBrains

Transcription

1 Agile letvægts projektstyring med Google PROSA, 31/ Thomas Blomseth, BestBrains

2

3 Tool types Physical tools Index cards on whiteboards Wall paper Lightweight general tools Office suites Google Docs Specialized tools Rally ScrumWorks TargetProcess Team Foundation Server from Microsoft VersionOne XPlanner

4 Benefits Lightweight No installation needed Easy maintenance of access and rights Same usability and flexibility as physical taskboard (nearly) Realtime collaboration Good for distributed teams Supports online meetings very well (spreadsheets in particular) Version control and tracking Built in Who changed what when and ability to revert Flexible Tools can be changed and improved easily Kaizen improvement of process can take place continuously

5 Lightweight process - Scrum Sprint Planning - Prioritization - Task breakdown - Team commitment - Sprint backlog Daily Scrum minutes - Three questions Progress Charts - Sprint - Release Product Owner - Speaks on behalf of the customer - Prioritization - Owns product backlog Scrum Master - Responsible for process - Support of team - Remove empediments Sprint Review - Demo - Retrospective Scrum Team - Cross-functional - Delivers

6 Google Docs for Agile The core of an Agile development process Taskboard and daily meetings Burndown and other visualizations of process Product backlog Retrospectives and process improvement Collaborative estimation using planning poker Release planning

7 Physical task board

8 Basic task board in Google Docs

9 Task boards in Google Docs Visualization of process state using text, numbers and graphics Well-suited for distributed contexts as everybody is able to see the same Realtime updates goes to all participants of the daily meeting regardless of location History, versioning, and access control is built in Please note: Can also easily be used for Kanban boards

10 Record and visualize process data Types of diagrams Burndown Cumulative flow Velocity etc. Record data daily in tables

11 Tracking and visualization of process metrics Gathering process data is easy Cumulative flow diagrams are useful

12 Backlog in Google Docs

13 Backlogs in Google Docs All participants can view the backlog One version of the truth Backlog is always up-to-date No need to send docs around which version is the canonical? Backlog is not hidden on some network drive Search makes it easy to find Backlog is a prioritized list = perfect in a spreadsheet

14 Planning poker in Google Docs The best planning poker application we ve seen Easy to do together with backlog in a Google spreadsheet Relies on realtime collaboration features Cells being edited are greyed out preventing premature disclosure of estimates

15 Planning poker setup

16 Playing planning poker

17 Release planning in Google Docs Cross-team distributed release planning is possible Good for supporting collaborative release planning process We have used process inspired in part by Last PlannerTM from construction Teams share their best plans and negotiate to get the best joint release plan Release planning spreadsheet used during Scrum-of-Scrums for shared view

18 Release planning in Google Docs

19 Retrospectives in Google Docs To Keep Problems To Avoid To Try Facilitating change to the better

20 Retrospective

21 Welcome to Japan!

22 Mieruka Japanese for we can see to take action Concept used by Toyota Creating participation through shared information

23 BestBrains Mieruka framework Fetching data from Google Docs (and other sources) to be able to display it with high visibility

24

25

26

27 Mieruka display at the office

28 Pieces of advice Make it simple Make it easy to change Adapt tools to processes

29 Tak!