Hi Mark,

This sort of approach sounds interesting - let me state my problem and have the 
developer come up with a solution.  Then I will see if what is produced meets 
my expectations!  That to me leaves it very open ended - it particularly 
favours the user and not really the developer.  

Now I can understand this sort of approach if you are talking about a concept, 
in other words this is the problem - we have no idea of a solution.  A typical 
case being the advanced filtering in MLO - it was left to Andrey to interpret 
the user stories/requirements and come up with a solution. But in this case the 
solution has already been put forward - a calendar. To expect the developer to 
go away develop the solution then present it for user critique sounds a big ask 
in this instance.  Only because of the various multiple connotations that can 
come into play with regards to this feature. Without at least a basic spec 
being agreed you could find yourself with an endless development process. 

Now if we are saying the problem is one of workload balance - find me a 
solution. Then that is slightly different - I am all for exploring new and 
inventive ways of displaying this sort of information.  But for the most part 
that is not the case - the repeated requirement/solution is for MLO to have a 
calendar of some description. To my mind a lot of developers have already 
addressed this area - there are enough working examples out there for anybody 
to put together a specification.

Personally I think in this instance - the developer needs assistance (though I 
may be wrong).  The developer needs to know what it is that needs to be 
delivered - prior I think to even starting this undertaking.  If we are talking 
about a simple month view calendar with dated tasks showing - perhaps that 
could be done quickly with the minimal amount of effort. There may even be an 
add-on/plugin module that could address most of the development work.  If it is 
something more involved that has to be done from scratch - things will 
naturally take a lot longer.  In this case I think somebody needs to do the leg 
work - get some agreement from the user community on what is required and then 
present it as a detailed feature request.
 
All the best
 
Steve





Original message
From: "Mark Levison"  
To: [email protected]
Received: 22/12/2008 21:01:51
Subject: [MLO] Re: Calendar





On Sat, Dec 20, 2008 at 11:30 AM, Steve Wynn <[email protected]> 
wrote:

I personally don't know any software developers that prefer 'stories' of their 
user requirements - although I understand the meaning.

Well most developers in the agile community really on user stories to capture a 
customer's needs. From Wikipedia (which isn't bad in this case):

http://en.wikipedia.org/wiki/User_story

A user story is a software system requirement formulated as one or two 
sentences in the everyday or business language of the user. User stories are 
used under the Extreme Programming (XP) paradigm for the specification of 
requirements (together with acceptance tests) (XP). Each user story is limited, 
so it fits on a small paper note card — usually a 3×5 inches card — to ensure 
that it does not grow too large. The user stories should be written by the 
customers for a software project and are their main instrument to influence the 
development of the software.
User stories are a quick way of handling customer requirements without having 
to elaborate vast formalized requirement documents and without performing 
overloaded administrative tasks related to maintaining them. The intention with 
the user story is to be able to respond faster and with less overhead to 
rapidly changing real-world requirements.
A user story is an informal statement of the requirement as long as the 
correspondence of acceptance testing procedures is lacking. Before a user story 
is to be implemented, an appropriate acceptance procedure must be written by 
the customer to ensure by testing or otherwise determine whether the goals of 
the user story have been fulfilled. Some formalization finally happens when the 
developer accepts the user story and the acceptance procedure as his work 
specific order.
So in theory when Andrey comes to implement this he might show us some 
prototypical ideas (sketches effectively) and see if it meets our expectations. 
In this case  Andrey is in the rather odd position of not having a product 
owner/customer (in the Scrum/XP sense) so there is no one person (or even small 
committee) he test the ideas with.
  
  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. 

The agile approach agrees with the problem but not the solution. In this case 
the less specific the better. Instead when the developer is ready to start work 
they engage in a conversation with the customer. If you specify too much 
upfront you will find that your requirements and needs change over time and you 
suffer requirements churn.

I know in the years since we started discussing calendars in this forum my 
needs have done several changes, through nearly 180 degrees. Now all I want is 
something minimalist as I described in my two stories.
 



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.

Again from the perspective of Lean Thinking I think of all this detail upfront 
as a form a waste. The vast majority will go unused. Instead of over specifying 
I would wait until the last responsible moment to do any serious discussion or 
research on this. In this case the last responsible moment would be Andrey 
saying "I intend to start work on this feature in the next month".

Cheers
Mark


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