tag:blogger.com,1999:blog-8247464260990313410.post3978967417564016061..comments2023-12-19T20:32:30.912+08:00Comments on Web Wednesday : Ditch the GANTT charts, become AgileNapoleon Biggshttp://www.blogger.com/profile/05160876389847534972noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8247464260990313410.post-80072007164445607102008-02-06T07:39:00.000+08:002008-02-06T07:39:00.000+08:00The length of an agile project should still be est...The length of an agile project should still be estimated up front by story card units. A story card is a description of a small functionality together with testing requirements. Then the progress of the project is a measure of how many story cards were completed after each iteration. From that, we can calculate a velocity (speed of story cards being completed) and will be able to project the completion date and see how well the developers can estimate the tasks.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8247464260990313410.post-31335874772654786962008-02-01T14:30:00.000+08:002008-02-01T14:30:00.000+08:00Agile projects really end up being series of small...Agile projects really end up being series of smaller 30 day or 6 week scrums. Each of which, essentially, is a project. Too many people seem to use Agile methodologies to justify Laissez-faire management techniques. <BR/><BR/>In the end, developers hate being managed, and <A HREF="http://www.envisionsoftware.com/Management/Peter_Principle.html" REL="nofollow">Peter Principled</A> managers who came from the development world will certainly stand up for their brethren with the "we'll get done what we get done when it gets done" siren song of Agile Development.<BR/><BR/>But, in the end, if you can't tell how long something's going to take, and you don't track how long it really took then you don't get better at making accurate estimates.<BR/><BR/>Now, otoh, I absolutely detest the concept of a project office mandating that you are "done with design" or "done with requirements" just because you've started the "next phase" of the SDLC.<BR/><BR/>So, the answer? You have to have some structure, or your developers will walk all over you. But you can't have TOO much structure, or your developers will walk OUT on you.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8247464260990313410.post-49826111060493442922008-02-01T07:44:00.000+08:002008-02-01T07:44:00.000+08:00Great post. Agile development is definitely becomi...Great post. Agile development is definitely becoming a new standard. However, I wouldn't go so far as to say we should ditch the Gantt charts. But they definitely need to be rethought. <BR/><BR/>We've used agile development to build web-based project management software called <A HREF="http://www.myintervals.com" REL="nofollow" TITLE="Intervals">Intervals</A>. We started out with the same ideals; let's throw out the Gantt chart. But we are finding that it does have some uses (timeline visualization, for one) and are in the middle of redefining the Gantt chart. We hope to have a lightweight version online soon. <BR/><BR/>Your insight will be valuable as we progress in this direction.jjrivhttps://www.blogger.com/profile/15903971177129603875noreply@blogger.com