Geneca’s “Getting Predictable”^SM Approach to Software Development Provides Unprecedented Alignment Around Delivering Business Value

Our Getting Predictable methodology is a highly focused approach that prioritizes features and functions in terms of the business value they represent. The following steps demonstrate how we evolve a project from conception to delivery.

We start with building common vision and objectives between stakeholders:

• Business Process Analysis (BPA) and Business Process Scenarios (BPS): When starting any software project, getting the project charter, vision and scope defined is a crucial step. Using a facilitated workshop approach, we drive a common vision and success criteria across all stakeholders.

  We don’t just identify high level objectives. Rather, we identify workflows and scenarios that capture the “intent” and business acceptance criteria of the system. Because acceptance criteria is identified before development starts, rework, critical defects and ambiguities are eliminated. We do this in days, not months!

Next, we define common metrics between IT and the business. Our goal is for IT and the business to have a common view of progress across the program.

• Interface Counting: Here, we quantify what it takes to build and deliver each scenario.  Working with program sponsors, we identify interfaces, reports, system integration points and internal engines. Once this step is done, the business can test completeness by saying, “If I have these interfaces, including x, y, and z, then I can complete these scenarios with no further development.” The benefits of Interface Counting include the development of trackable, repeatable metrics.

  Change control is quantifiable.  Your organization will experience unprecedented control and visibility using these metrics.

• Low Fidelity Prototyping: This kind of prototyping enables us to develop paper prototypes of the business scenarios defined for a system. This kind of prototyping can be completed in hours, rather than weeks and generates quick feedback. Prototypes are built by the business team providing the requirements.  Once this step is complete, the business can answer the question, “Is this really what I am going to get?”

  In days, your team can estimate and prototype your system, eliminating ambiguity and rework in the development phases.