As an OGH developer, I've seen specs range from 'gimme something that works' to docs the size of phonebooks. No matter how they're presented, specs are only the starting point for understanding what needs to be built. Screen shots are as good a starting point as anything else: they show how the user understands their process. However it starts, by the end of a design phase, the list of requirements should be understood by everyone involved.
I am NOT a Scrum Master (I only sound like one in meetings), but I have been on Agile teams in several client organizations. When it works, which has been most places, it works well for ARS teams. Agile takes the app dev cycle from years to days; you don't get as much done in a cycle, but you get more of them. It also helps larger projects with armies of developers. A few screen shots can become prototype forms very quickly. Reviewing prototype forms opens the discussion for workflow requirements. Several short cycles later, the prototype proves all the concepts and has identified 'real' specs. The end result will certainly be different than the original screen shots: it will have workflow! HTH, Joel Joel Sender jdsen...@earthlink.net 310.829.5552 From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Robert Heverley Sent: Thursday, August 16, 2012 12:00 PM To: arslist@ARSLIST.ORG Subject: Re: Building A Custom Application (Just Checking) ** I always say: "It's like building the house without the blue prints, it doesn't work".. On Thu, Aug 16, 2012 at 10:56 AM, David M. Clark <david.m.cl...@tn.gov> wrote: ** I've written several applications from elaborate requirements documents that make no reference whatsoever as to what the finished app should look like. Screenshots only would be a refreshing change compared to that. _____ From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Susan Palmer Sent: Thursday, August 16, 2012 1:53 PM To: arslist@ARSLIST.ORG Subject: Re: Building A Custom Application (Just Checking) ** Oh yea 'agile' development ... went through that here a few years back .... it was not a pleasant experience on the Remedy side especially if you like to do your work once with maybe occasional changes. You all overlooked something even more basic than not knowing what the processes are required behind the field for workflow ... what's the character length? I love custom applications (mine) but I can tell you that after 10 years of working in it from birth to current I would love to rewrite it and take out all the 'stuff' everyone had to have 'right now'. After a while it's very hard to extract things that don't get used. And, there never seems to be the time! Susan On Thu, Aug 16, 2012 at 1:32 PM, David M. Clark <david.m.cl...@tn.gov> wrote: <snip> _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
