http://caramelwhistle.com/2009/03/09/planning-enough-time-to-do-it/ Scout, Design, Film, and Thought Provoking stuff Fri, 16 Apr 2010 02:53:42 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://caramelwhistle.com/2009/03/09/planning-enough-time-to-do-it/comment-page-1/#comment-75 Karsithe Mon, 09 Mar 2009 22:33:32 +0000 http://caramelwhistle.com/?p=284#comment-75 Thanks for the thoughts and suggestions. One of the key reasons we are using SCRUM for our project is that we need to be able to make changes as quickly and cheaply as possible throughout development. Even with a completed, well thought through plan, it's still necessary to constantly refine the design as you find out what's "fun". We were also using several different poorly-documented open-source components which we weren't able to fully test before we began. I think the real problem is that we didn't consider how long meetings would take when we worked our how much time we had to spend on this project. I'm not saying we should cut down weekly development time to 5 hours and spend the rest on meetings, just that it would have been easier to estimate how much time to put aside. Guess we know for next time :P Thanks for the thoughts and suggestions. One of the key reasons we are using SCRUM for our project is that we need to be able to make changes as quickly and cheaply as possible throughout development. Even with a completed, well thought through plan, it’s still necessary to constantly refine the design as you find out what’s “fun”. We were also using several different poorly-documented open-source components which we weren’t able to fully test before we began.
I think the real problem is that we didn’t consider how long meetings would take when we worked our how much time we had to spend on this project. I’m not saying we should cut down weekly development time to 5 hours and spend the rest on meetings, just that it would have been easier to estimate how much time to put aside. Guess we know for next time

]]>