Agile Project Management

A presentation and workshop for MSU Libraries' Digital Scholarship Collaborative.

Transcript

1. AGILE PROJECT MANAGEMENT a Digital Scholarship Collaborative workshop Robin Dean, Digital Projects Librarian MSU Libraries rdean@msu.edu July 12, 2016
2. agility It’s easier to change course when you take small steps. “Curlew Sandpiper” by flickr user Kev Chapman, CC BY 2.0
3. iterative and adaptive 1. Do a little bit. 2. How did that go? 3. Do a little bit more, a little bit better. “Chameleon” by flickr user Christopher Evans, CC BY 2.0
4. agile software development How do we build software that people want? How do we build good software faster? How do we stop doing things that aren’t important? (How do we make more money?) http://www.agilemanifesto.org/ http://agilemanifesto.org/principles.html
5. MSU Libraries Digital Repository Team Aaron Collie Nathan Collins Robin Dean Sruthin Gaddam Devin Higgins Megan Kudzia Lucas Mak Megan Schanz Nicole Smeltekop Electronic Theses & Dissertations Grange Newspapers Duane Mezga Holocaust Sites Photographs MICHILAC Women’s Overseas Service League Oral Histories
6. Questions we had trouble answering 1. What are all the things we could be working on? 2. What is the most important thing to work on right now? 3. How do we know if things are stalled? 4. How do we know how much we can get done? 5. How do we know when work is done? 6. What if priorities change? Who can change priorities? “Sandpipers” by flickr user Alan Kotok, CC BY 2.0
7. Scrum: everyone moves the ball “Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.” http://www.scrumguides.org/ Photo by Yuval Gelber [Public domain], via Wikimedia Commons
8. Scrum Roles Product Owner: “What do our users want?” • Communicates with stakeholders • Sets priorities for the team Developers: “How do we build it?” • Make technical decisions • Estimate how much can get done Scrum Master: “How can we work better together?” • Coaches the team on agile processes • Removes impediments to progress
9. Sprints: working iteratively Each sprint is a block of time for getting things done. After each sprint, the team reflects, gets feedback, and makes improvements. DO IMPROVE
10. Scrum Meetings Sprint Planning (1 hour) What are the most important things to do in the next two weeks? Daily Scrum (15 minutes every day) How is the work going today? Sprint Review (1 hour) What did we get done, and what do you think about it? Sprint Retrospective (1 hour) How can we work better together next time?
11. Sprint lifecycle (1-week sprint) Sprint Planning Sprint Day 1 Daily Scrum Sprint Day 2 Daily Scrum Sprint Day 3 Daily Scrum Sprint Day 4 Daily Scrum Sprint Day 5 Daily Scrum Sprint Review Sprint Retrospective
12. Scrum Documents Product backlog A prioritized list of everything that could be worked on Backlog item A piece of work to be done Definition of done Guidelines for knowing whether you’ve finished an item
13. Exercise: Make a project backlog 1. Look at your table’s project card. 2. Working alone, write down two tasks that need to get done at any time during the project. 3. In a group, put the tasks in the order they should be done. (You can group duplicates and related tasks together.) 4. Pick a spokesperson. Time: 8 minutes
14. Estimation “How do we know how much we can get done?” … during each sprint … within the same team … by a certain point in time
15. Relative complexity Small Medium Large
16. Exercise: Estimate your tasks For each one of the unique tasks in your backlog, decide in a group if it is a small, medium, or large task. Small tasks take less than 2 days Medium tasks take less than 2 weeks Large tasks take more than 2 weeks When you’re done, pick a new spokesperson. Time: 8 minutes
17. Sprint backlog A list of tasks the team commits to finishing in one sprint. Getting work done is the responsibility of the whole team. How many people are on your team? How available are they during the sprint? What special skills do they have?
18. Exercise: Create a sprint backlog 1. Add two weeks’ worth of tasks to your team’s backlog. 2. Prioritize the tasks in the order they need to get done. 3. Pick a new spokesperson. Hint: Don’t include any large tasks…they take longer than 2 weeks! Time: 8 Minutes
19. Congratulations, agile teams! Questions? “Sandpipers” by flickr user U.S. Fish and Wildlife Service Northeast Region, CC BY 2.0