Friday 16 May 2014

CAAD Codeless Situational Applications Development Methods for Analysts

CAAD Methods

I produced this article to describe how analysts can build enterprise-scale situational applications time and again without coding based on the methods adopted by the team at Encanvas over the past decade.  The methodology hasn't changed too much over the past few years but we continue to learn from customers and practitioners.

It's only in the last three or four years that we've honed the use of Outcome Driven Innovation (ODI) and Blue Ocean methods as part of this approach.

One of the factors that we've found critical to success is to specify the requirements, outcomes, user group structures, reporting needs (RPRS Analysis) etc. BEFORE jumping into a meeting room and workshopping solutions.

It's great to work in a collaborative way but having the structures and outcomes buttonned down means that analysts can get to work on the boring 'basic modelling' of a solution and have something to walk around before users and stakeholders start iterating their design.

I hope you find it helpful!

I.

Keywords:
Codeless software development, CAAD, Software Development Methods, Agile Software Development Methods, Encanvas, Enterprise Situational Applications Development Methods

No comments:

Post a Comment