I am not saying that Agile doesn't work - its just not a one size fits all solution. Re 3 projects: er real world. Two clients come along both offering interesting pieces of work that they want me to start on soon - neither requires a full time commitment (they need to organise workshops. there are delays while tenders are issued, etc) ; neither is prepared to wait. Plus trying run my business (writing proposals for new work - normally to some sort of deadline; accounts and tax submissions need to be prepared; conferences to be attended). Plus life (major project at the moment: trying to clear my mother's house by the end of the end of the month). All of these have deadlines, fixed points (workshops, etc) and other constraints which means that planning ahead on a day by day basis is the only way I can manage my work. Your world may be different but I suspect my world is more recognisable to most. And sadly MLO provides little help in this planning ahead. Its quite good a helping me manage my immediate workload (but see other posts re manual order) but useless at helping me work out when I am going to get particular pieces of work done, etc. Which is frustrating as all the tasks that I have got to do are actually in MLO - its just that it does provide the views/data that I need to do the planning. Hence anything like a Gantt chart or Calendar view would be a major improvement as far as I am concerned.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mark Levison Sent: 13 March 2009 8:45 p To: [email protected] Subject: [MLO] Re: Feature Request: gant view. 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-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 -~----------~----~----~----~------~----~------~--~---
