Caution!

Visiting this web site requires a newer version of Netscape Communicator.

Visit Microsoft's Web site to obtain the newest version of Internet Explorer, or visit Netscape's Web site to obtain the newest version of Netscape Communicator.

Visiting this web site without first upgrading your browser may result in unreliable behavior.








Agile Alliance




JAY CONNE CONSULTING



Consulting


Agile - What is it?


Agile/Scrum/XP Training


Agile Testing - a Summary


Agile for Embedded Software


Technical Education


Burndown and Velocity Example


Contact


Presentations and Tools


Resume .doc

Special Projects



Wisdom


Laissez-Faire Capitalism


Robotic Parking


Water Language - Clear Methods


OPN - Object Process Network

Professional Associations



ACM


SPIN

PRACTICAL PHILOSOPHY



H.D.B. Book Proposal




    Consulting

Jay Conne Consulting  

jay@jconne.com  






Design Discipline:

Building effective business solutions requires multiple dimensions of understanding.  Depending upon the size and risk of the project, this discipline is tuned to the appropriate formality from ad hoc to fully specified.  With a Lean/Agile approach, these dimensions are applied at a global level to the degree necessary to enable applying them locally and iteratively on small increments of business value. 


Analysis Dimensions:  

  1. Scope – The business scope to be coherently managed – systems that are not designed to work together are unlikely to. 
  2. Business – The prioritized essential factors for business success including the risk focus (below).  "Use Case" analysis identifies contextually specific usage requirements.  
  3. Data – The objects in the world we need to track with their attributes and the relationships between those objects, i.e. Data Architecture with Conceptual, Logical and Physical Models.  
  4. Process – Identify the key processes and their steps, e.g. a business process workflow or a manufacturing sequence.  These are initially expressed as data-flow diagrams and later as more detailed state diagrams.  A unit of work, such as a customer order, or a custom product build, moves through a series of states in its lifecycle.  Each state transition can only take place when certain business rules are satisfied. 
  5. Risk – Identify specific business and technical risks, their business value, and mitigating strategies for each.  Risks are also inherent in the requirements process where too narrow a perspective typically yields unsatisfactory solutions.  See scope focus (above).  
  6. Usability – Verify the system’s usability and effectiveness from early design through deliverable project.  Initially use rapid paper prototyping and later the deliverable system.  Catch errors in assumptions and design as early as possible for cost and time effectiveness.  (Please see: www.uie.com for more information on this topic.)  Can users of your website find what they want easily enough so that they don't give up in frustration? 

RESUME










Jay Conne Consulting
617-776-0339 -- jconne@gmail.com
© 1993-2013...





Sign In