We help organizations to identify requirements in the context of helping them to achieve strategic goals through internal changes to organizational capabilities, policies and processes, through the development of Technology Systems.
We focus on analyzing end-to-end processes that create value, and automating unnecessary, non-value added work.
A long-standing problem in business is how to get the best return from IT investments, which are generally very expensive and of critical, often strategic, importance. One way to assess these goals is to measure the ROI or return on investment for all projects.
According to Forrester Research, more than $100 billion is spent annually in the U.S. on custom and internally developed software projects.
Rework is one of the largest headaches facing organizations and it has become so common that it is actually built into the project budget and timeline. Estimates of rework on typical projects ranges between 20% and 30% of total project budget. Rework impacts the entire software development process from definition to coding and testing.
One of the reasons for rework is that the requirements engineering and definition process is broken in most organizations and there is a huge disconnect between the business and technical sides of a project. While various technical solutions have helped make developers, coders and testers more efficient, very few solutions have been targeted at the business analysis stage.
Experts estimate that 10% to 40% of the features in new software applications are unnecessary or go unused.
We always ensure that requirements must be measurable, testable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design. We use a combination of techniques including facilitating focus groups or requirements workshops together with visual and workflow prototyping, and use cases.
Our Best Practice approach takes the list of requirements merely as clues and ask 'why?’ repeatedly, until the actual business purposes are discovered. Once the small set of critical, measured goals has been established, rapid prototyping and short iterative development phases of working software are delivering value long before the project is half way.