As mentioned previously, a friend and I have begun a mini project of our own. Since we both have a keen interest in the Agile methodology, it’s always interesting to see different versions and ways of implementation. As certified Scrummasters, we can think of no better way to try new ideas than by using Scrum in our own project.
Over the next few weeks, I’ll release different parts on things we tried differently in Scrum and share views on whether our technique worked in a small group, whether it will work in a large group, share views on things that we triumphed on and things that needed improvement. Feel free to share your thoughts and experiences in the comments section as well.
Part 1 will focus primarily on the project set-up. Because the mini project consists of only 2 developers/scrummasters/product owners/stakeholders, we decided there were many things that could simplified on. The fundamentals such as the taskboard/stand-ups/backlog etc were still crucial but as a start, we made the following changes:
- Virtual taskboard/backlog: We decided to combine the taskboard/backlog into one. We utilised a shared Google spreadsheet where we would both have running constantly on our machines respectively.
- Mini Sprints: Time period, 1 day.
- Stand-ups/Sprint review/Sprint retrospective: Combined version, still well within our 5 minute timebox, we would review yesterday’s sprint, re-organise the new day’s work as well as provide feedback to each other.
Early indications so far, from a development point of view, things are progressing along nicely although due to the shortness of mini sprints, it does promote a sense of urgency and failure to meet the tasks obviously becomes more evident. However, this is still working for us as with no business deliverable pressure, there’s always room for leniency between friends. And in terms of progress, it fulfills both our satisfactory levels, so the stakeholders are happy.
Next part of this series will be on the virtual taskboard/backlog, is it working? Will it work in a bigger team? Can it be done better?
Feedback and suggestions always welcomed. Until then, see you in Part 2.
Image taken from https://www.scrumalliance.org/why-scrum