Excellent point, Mark. I would certainly sign up to the first two user stories. At the moment, I do both of these activities but outside MLO. Richard
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mark Levison Sent: 17 December 2008 2:56 p To: [email protected] Subject: [MLO] Re: Calendar In the Agile Software Development world, we don't out right tell a developer exactly what we need. Instead we write stories that describe a problem we want solved and provide a business value. In this case some stories might: As a busy person with many projects I want to be able to see the tasks I have committed day by day for the next month because this would allow me to spot when I'm over committed. As a busy person with many projects I want to be able to move tasks quickly from one day to another to help me balance my commitments. As a MLO user I want a calendar because it looks cool. ... Using this format we get to understand what everyone really wants from a calendar without the endless discussion of what exactly a Calendar is. The business value will help Andrey figure out what matters most. If we just keep demanding a calendar, Andrey will slave away for months and the result won't be close to satisfying anyone's needs. Cheers Mark On Wed, Dec 17, 2008 at 7:41 AM, Steve Wynn <[email protected]> wrote: Define 'simple' calendar? As the champion of the 'no calendar in MLO group' (self proclaimed ) I would be interested in the interpretation of simple. If you search the previous messages in the group on calendar you will see we have had some interesting debates on this topic. Though I don't ever think we reached a resolution. I think the majority consensus (though I may be wrong) is to have more of a time-line function within MLO to link more into the project related aspects. Saying that I think we probably still have two entrenched camps, those for a calendar and those against. Personally I am not opposed to a calendar as such, but it is such a generic term that has a multitude of meanings that I think from a development point of view specifics are required. I am not so sure the specifics have yet to be defined - though many people have put forward their own take on the requirements. What the 'for calendar' group need is a champion, to bring together all of the information so far received. Then personally I think somebody needs to come up with a technical specification that can then be posted for review. There also needs to be some solid justification, people using MLO at the moment are obviously using something else for this function (I use Chaos Intellect). So how is MLO going to draw users away from their current application? Is the answer to have a calendar or closer integration with existing calendar applications? Calendars link to scheduling, which links to contacts - which link to more of a PIM based app - personally I already have a PIM so see no advantage in MLO becoming one. I can always come up with more questions than answers on this one, a simple plug-in calendar module might suit the requirements. If that could be done with minimal development time and would be taken 'as is' then I would give a yes vote. But my concerns is that focus will be directed to the 'calendar' and the development of this feature, in other words it will not be a static component. Do we really want MLO Development to be spent on calendar functionality? Especially when to me, Time&Chaos, Intellect, Outlook, Google, Sunbird - to name just a few - do this well at the moment. I also think 'simple' might translate as being pretty useless for the bulk of MLO users - without added functionality. I think there is a feeling, more than a proven certainty, that a calendar in MLO is going to be an improvement. Being able to visualise the workload as a main consideration. Personally I am not so sure a calendar meets this requirement. A list of tasks on a given day to me does not really aid that much with planning or workload balance. I think other things might be instigated to better achieve this - graphical progress bars on projects - percentage completion scores more visible - gant charts - pie charts - better reporting. Anyway, thought I better chime in before the 'for calendar' momentum started to get overwhelming. I think there is a lot to think about with regards to this overall. All the best Steve ----- Original message ---------------------------------------- From: Ciaran To: MyLifeOrganized Received: 16/12/2008 15:31:51 Subject: [MLO] Calendar >A simple Calendar function in MLO would be a distinct >advantage, >containing dated tasks. Without a calendar, it is very >difficult to >track appointments when completing a week's tasks, for >example. > All the best Steve -- 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 -~----------~----~----~----~------~----~------~--~---
<<inline: big_grin.gif>>
