Hi Grant, I admit I have next to no experience in designing solutions and products. But I do have experience in delivering solutions to users and to me there can be a world of difference between user requirements - and final delivery. Anybody that has worked a Support role and acts as the buffer between developers and users - normally has a good understanding of the difference that can exist between the developer's world and the user's world. Andrey is also a user - so he is aware of the limitations already of MLO and the issues that arise. In a way that to me is why MLO is so robust and reliable. Making a sweeping statement here - but if more developers used their own products in anger, perhaps software as a whole would be a lot better.
In the end a technical specification can aid the developer, if it detailed, in the decision making process. Here I don't even think the terms have been probably defined in this instance - what is a calendar? If we have no agreement or definition of terms we could all be talking about different things? You may think I am not being constructive about this - but I feel we lack even a starting point at the moment. Relaying user stories is all well and good - but a calendar has been on the cards for a long long time now. Are we any further on from the start? Personally I don't think so. My idea of the technical spec and user agreement was in an attempt to move this forward - so you state this is what 'we' want, 'we' being the users that have requested this functionality. Which can then be presented to Andrey and he will be able to supply a response. Get this issue resolved once and for all. All we have on a regular basis at the moment is a request for a calendar in MLO appearing - it never moves forward from there. Yes I am concerned that if this feature is agreed and accepted - the next 12 months plus will be devoted to this endeavour. MLO is a brilliant product at the moment - without a calendar. The recent changes in the new Beta version once again surpass my expectations. I cannot see that a strong enough argument has been put forward to devote development time - which to me is being spent on the right functionality to improve MLO - to a calendar. Especially, as I keep saying, when so much if left open to interpretation and people are already using alternative means to address this area. I still hold the opinion that people make an assumption that a calendar will resolve the issues they have mentioned - only because it is a solution seen in other products. I am not so sure. I also hold to the belief that most functionality to reproduce a calendar is available in MLO - through adjustments and structure of the Outline. It is manually orientated but it can be done. MLO to my mind also has sufficient (although not graphical) views to display workload balance and custom views can also be created. Personally to address the area of graphical representation - again the last thing I would want is a calendar - I would like charts, time-lines, status indicators etc. As always this issue leaves me with more questions than answers - but I seriously think if you want to be constructive about this issue. Questions need to be asked and answered. What working systems are we addressing? What user group? What market? I use GoalEnforcer a similar product to MLO that gives me a visual representation of my goals. This includes a month view calendar - which I find I have no use for at all - it filters on due date/start date/finish date. What I do find useful is a line chart that shows me a time-line and my status. What I do find useful is visible percentage scores on goals - colour coded for status. A Hyperfocus Zone to target specific items. A status report that can be zoomed in on a particular area. I also utilise a combination of DIT and The Now Habit - so I am a heavy schedule/calendar user. I schedule 24 hours a day, 7 days a week (using the Unschedule). My working system relies on a calendar - I personally found Chaos Intellect to be ideal. MLO is utilised for my projects and I find that ideal - it has the right level of functionality, simplicity and reliability. So personally I tend to find the best tool that suits me and my requirements - so as a benchmark for MLO to pull me away from my current calendar application it would need some type of 'new' functionality that is not available in Chaos Intellect. Chaos Software have been developing Time&Chaos (and recently Intellect built on Time&Chaos) since 1992 so in terms of development time and effort they have a lead. So a calendar in MLO holds little to no perceived value to me personally at the moment. I also have trouble seeing the perceived value others find in the request for this feature - considering all of the above. As a separate argument where I do see value, both for me, and for other Chaos Intellect users is in MLO integration with Chaos Intellect. That to me would be a better use of time and resources, it has an existing user base. Projects are not addressed in Chaos Intellect it is a PIM - so it has no real project functionality an area that MLO could exploit. It does have some limited tree view structure so possibly could be expanded. I believe it may also be written in Delphi (though not 100% sure on that) so perhaps will be relatively easy to make a link. Chaos Software do work with third parties to address specific areas - Companionlink for PPC link. Chaos Intellect is Time&Chaos with an email module - so actually two user bases are addressed if it works in Intellect it will work for Time&Chaos (based on same database structure). Chaos Software have a Legal Billing module for time recording, costing and invoices - perhaps that could also integrate with MLO as it addresses the In tellect database so perhaps that could be used as a conduit. There is a Web version of Intellect so perhaps MLO could somehow hook into this in some sort of fashion. Chaos Intellect addresses all the areas currently not addressed in MLO - contacts/email/calendar - so it could be an ideal way to address this area and provide a solution. Chaos Intellect is relatively inexpensive compared to other products of the same nature $59.95 - perhaps a bundle deal could be produced that could benefit both parties. That to me would be another way forward - not only from my own personal viewpoint but also from a Business/Tactical viewpoint. But all said and done if I knew what people were actually requesting - if it was defined and had some justifications. I probably wouldn't be as objectionable as I am at the moment. Fair enough people want it - I just think not enough is coming forward in terms of justification, perceived value, requirements, target market, target systems etc. If you were to say to Andrey the inclusion of a calendar in MLO would address a particular working system/methodology that MLO doesn't address at the moment - that has a major user base - MLO would probably have a calendar sooner rather than later. As somebody against the idea, it shouldn't really be me that is pointing all of this out. Apologies if I come across as being on a high horse about this issue, but as I mentioned before it seems to me a 'big ask' of the developer in this instance without further clarity. If a real debate is started about the specific requirements then I would do my best to be constructive. But at the moment while this floats around as it stands I will continue to oppose it due to the various reasons I have already put forward. Merry Xmas All the best Steve ----- Original message ---------------------------------------- From: Grant <[email protected]> To: MyLifeOrganized <[email protected]> Received: 24/12/2008 10:53:42 Subject: [MLO] Re: Calendar >Steve, with all due respect to 'discussing views' I wish >you would get >off your high horse of fighting the implementation of a >calandar. >People want it. From what I have read they only want it >as a 'view' >and are happy to have it depend on the existing MLO >input, data, and >management. You keep fighting because you seem to see >it as some >giant monster of functionality - I agree, right now we >dont want >this. But mainly why don't you help with constructive >ideas on what >it could be, instead of fight this all the time. >I had some respect for you opinions and views, but your >last one on >the Agile view, alas, suggests some lack of long term >experience in >designing solutions and products, as opposed to, perhaps, >developing >them. TimV is right, you need to architect, and there >you always >start with the user needs (which is a subset of desires) >then the >processes (user senarios), then the information and >process >architecture, then the IT Architecture to support it, >and that gives >the developer something they can work on that has >specifications that >can be build against and are testable, both by the >designers, but >also, key by the users. >Merry Xmas! >Grant > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
