OK - standard Scrum type stuff. May work OK (or not, depending on your view) in a production line type environment where you have a group of programmers churning out chunks of similar code so what you did last week is some guide to what you are going to be doing this week (incidentally these concepts are not new, I remember reading an article by Tom Gilb in 1984 in which he said that the best source of information for planning purposes is your current rate of progress on your current project) . However, when you always seem to be doing new things so this weeks activity is completely different to last weeks activity and you are working on three different projects each with their own dependencies and delays and deadlines, it is of limited value (as far as I can see) Richard
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mark Levison Sent: 13 March 2009 1:59 p To: [email protected] Subject: [MLO] Re: Feature Request: gant view. On Thu, Mar 12, 2009 at 5:32 PM, Richard Collings <[email protected]> wrote: Agile people do like their little aphorisms. :-) Thanks we like to think we're witty too. However, I am intrigued - how do you plan? Somebody says to you, 'when can you get this done by?' how do you work it out? Burn down charts and a cone of uncertainity - usually +/- 30%. Key points: - we don't track task hours, we track stories (sometimes we use sizes but just relative numbers not absolute i.e. no days) - we use the number of stories completed in a week (or a day if need be) as velocity. - we average the last three weeks (or iterations worth) to tell us how much we're getting done on average. - we use that to see how long it will take to get through the customer requirements (aka the backlog) - finally we use a cone of uncertainity that narrows as we get closer to being done (can't find a good picture right now). One approach with a lot of detail: http://alistair.cockburn.us/Earned-value+and+burn+charts Much more detail another time. I teach a three day course in Agile Software Development - Planning and Estimation is probably a half day. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mark Levison Sent: 12 March 2009 4:50 p To: [email protected] Subject: [MLO] Re: Feature Request: gant view. What benefit would you (and the rest of us) derive from a Gnatt view? Part of what I do as an Agile Coach is wean people from their addiction to MS Project and Gnatt views. I usually point out that Gnatt never tells you when you will be done, only the first moment you won't be done. Cheers Mark On 3/11/09, mlo addict <[email protected]> wrote: I love using mlo but am missing a gantt view. I would like to request a gantt view like proj...@hand has. See http://www.natara.com/ProjectAtHand2/ScreenShots.cfm Kind regards, Mike Recent Entries: Agile/Scrum Smells: http://www.notesfromatooluser.com/2008/06/agilescrum-smells.html Agile Games for Making Retrospectives Interesting: http://www.notesfromatooluser.com/2008/10/agile-games-for-making-retrospecti ves-interesting.html -- Cheers Mark Levison Blog: http://www.notesfromatooluser.com/ Recent Entries: Agile/Scrum Smells: http://www.notesfromatooluser.com/2008/06/agilescrum-smells.html Agile Games for Making Retrospectives Interesting: http://www.notesfromatooluser.com/2008/10/agile-games-for-making-retrospecti ves-interesting.html --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/myLifeOrganized?hl=en -~----------~----~----~----~------~----~------~--~---
