This is the next in the series of entries about Demo Showcase Suite and the goals I wanted to accomplish.
5. I wanted the team to feel the urgency of working hard and smart early in the project to avoid the death march mindset at the end
Here were the things we knew, right at the start of the project:
a) The deadline was July 13th. It was not moving. No matter how many times I wished we had a few more months, weeks, days (or even hours), we were launching during the keynote on opening day of WPC.
b) We had huge technological hurdles to overcome on areas we had never seen before.
c) The customer wanted frequent updates on the work, samples of what we were doing.
To cope with all of this, we implemented some project management processes
1) We broke the project into 3 week sprints. This was our first time doing this, and I think we took the word sprint a little too seriously. We were always up against a deadline of some sort, but that was driven by the final, immovable deadline. When we saw our iterations slipping, we weren’t able to slide requirements to follow-on releases, but we did see that we were behind, and worked harder earlier in the project to get back on track. We also were able to keep the developers focused on the important features instead of getting wrapped around the axle on something that wasn’t supposed to be started for a couple of months.
Iterations worked for us as well, as we were able to better manage the customer expectations for the functions they would see in the next release. They knew what to expect, and knew what not to expect. That went a long way in keeping down the surprises for both parties.
In the end, we did one ‘Alpha’ release, two ‘Beta’ releases, and 3 ‘RTM’ releases. In retrospect, we should have called them Alpha 1, Alpha 2, Beta 1, Beta 2, Beta 3 and RTM 1 to properly set everyone’s expectations not just to the functionality, but to the quality, but that’s a lesson we learned the hard way.
2) We held a team scrum every day at 1:00 PM. We tried to keep this to 15 minutes a day, and I, as scrum master, tried to keep the team focused on three things:
i) What did you complete since the last scrum – Just a list, not a detailed dissertation. This helped everyone else know what was ready to test, or what dependency they had been waiting on was now complete.
ii) What are you working on between now and the next scrum - Just a list. If this was the same list you provided the day before, we hadn’t broken the tasks down far enough. If that continued for more than a few days in a row, it was time to take it off line, break down the tasks some more, and add resources if needed.
iii) What red flags are still outstanding that are keeping you from completing your work – Details as needed, especially if the task was taking much longer than expected or progress could not be made without more help
We tracked all of the tasks in TFS, though not as consistently as I would have liked, and added details / blocked status as needed.
At the end of the scrum, I stepped in to try to work any red flag issues to get the tasks back to green flag with each developer.
I’m a morning, person, and do my most effective work early in the day, so holding the scrum later in the day enabled me to break my day into two pieces. Some days, some of the red flag issues carried over to the next morning, but usually, I was able to focus on the big picture tasks that were assigned to me in the morning. The afternoon was spent solving problems, to keep the developers moving. It stopped a lot of wheel spinning (I’d like to think) and made sure no one was stuck on an island.
Having the daily scrums gave me, and the rest of the team, constant feedback on how we were doing to meet our next milestone, and how much effort we needed to drive into the current iteration that week to get it done. Sometimes that meant a weekend in February or March was spent in the office trying to clear up the backlog. But we knew we couldn’t grow the schedule, so it was better then, than to wait till the last minute when other problems would undoubtedly arise.
I know for absolute certainty that without these two processes, we could not have been successful. I also know that far more ‘project management’ time was charged to this project than was planned because of these scrums, but we probably saved just as much dev time by stopping the wheel spinning, and allowing me to focus on my tasks in the morning without constant interruptions. With a team of more than two developers on a project, I would absolutely do this again.