making software development predictable

Software Development

Our approach to software development is based on Getting PredictableSM best practices and virtually guarantees a successful software development effort. This is an iterative process that
allows for change and feedback loops to keep us on track with success criteria.

Every Geneca team has clearly defined responsibilities, including a leadership team with the following roles:

  • The Client Partner is accountable for making sure there is alignment between the project stakeholders and that the team delivers what the client needs.

  • The solution doesn’t function? Lots of defects? Then find the Architect! If fixing one issue uncovers three more, don’t talk to the Project Manager. Find the Architect! The architect is solely accountable for making sure things work technically.

  • If the system works, but the business can’t find the functionality they expect, seek out the Business Analyst or Quality Analyst (This can be the same individual). They are accountable for making sure requirements are met throughout the project cycle.

  • Of all the Project Manager’s roles, transparency is first and foremost. The Project Manager keeps everyone aware of decisions being made and identifies and removes obstacles that interfere with team success.

Upfront Requirements Definition: The Key to Project Success

Using Getting Predictable DefinitionSM, we work with all of the project stakeholders to get agreement on project success criteria – before a line of code is written or an estimate is made. We define scenarios in business terms and identify exactly what needs to happen in order for a scenario to be done, done, done. Next, the delivery team presents a release plan that includes the expected cost, duration, and resources required to successfully complete the project.

Once our upfront work is completed, development begins. Our emphasis on upfront requirements helps us do a better job reducing future rework, supporting change control, improving testing efficiencies and, most of all, meeting project objectives.