I personally don't know any software developers that prefer 'stories' of their 
user requirements - although I understand the meaning.  From my own experience 
developers always prefer specific's - they need to know what is required so 
they can deliver the requirement.  Sometimes if you assume a developer will see 
it a certain way because of what you have conveyed, even if you think it is 
common sense, you can be very much mistaken. To me the more specific, the 
better.  Where I think developers have major issues is in trying to get users 
to 'agree' on those specifics.    

Now in situations where the area is new or has not really been covered by other 
developers, then a certain amount of it will rely on relaying user experiences 
/ general requirements etc - then a lot is left to the  imagination of the 
developer to come up with an interpretation. But in this area of a 'calendar' 
there are enough alternative methods both electronic and manual that personally 
I think anybody who requests this feature should be able to supply specifics in 
detail. A detailed specification so that the word 'calendar' is not open to 
interpretation.  Everybody will then know what the user means by calendar - the 
requirements they are asking for and the functionality they want to see 
added/modified in MLO.

I personally don't want a calendar in MLO as it stands, but if I did I could 
come up with the specific requirements I would look for in that functionality.  
A few beneficial reasons as seen through my eyes. Then the types of 
user/working systems it would/wouldn't appeal to overall.

Now even if we had hundreds of technical specs produced - we would at least be 
able to see the patterns. Highlight the key areas and requirements - see the 
most requested type of 'calendar' interpretation - the most wanted views etc. 
We could start to narrow it down and reach agreements.  At the moment I have a 
rough understanding of what is required, some users have been quite detailed. 
Overall I don't see anything objectionable about it overall, but it still to me 
seems to be at the brainstorm mode and is a long way off from being passed to 
the developer as an actionable item/feature request.
 
All the best
 
Steve







Original message
From: "Mark Levison"  
To: [email protected]
Received: 17/12/2008 14:55:47
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-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
-~----------~----~----~----~------~----~------~--~---

<<inline: big_grin.gif>>

Reply via email to