On Fri, Mar 13, 2009 at 4:40 PM, Richard Collings <[email protected]>wrote:
> 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) . > We will differ on the limitations. I see Agile as way of managing change. Velocity works as long as you can do relative sizing. I know these concepts are not new, that doesn't mean they don't work. > > 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) > Why are you working on three different projects at once? That seems to be a way to deliver all of them later. Why not pick one and deliver it first? Mark - who sees the world rotated throught 90 degrees. 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-retrospectives-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 -~----------~----~----~----~------~----~------~--~---
