Bridging between people and technology
(Who’s minding the shop?) This blog is an attempt to stimulate discussion and understanding of the balance of responsibility for delivering business benefits from IT investment. It is now fairly widely recognised that this is not as simple as choosing a system, getting it working and reaping the benefits, but as yet we can call … Read more
“Bridger” A person who acts as go between or translator between the management of a business and it’s IT department or IT partners. The background Since the arrival of computers in the enterprise there has been an unfortunate and counterproductive power struggle between IT departments and other areas of the business. IT professionals share a … Read more
Sometimes the definition of requirements and management of their delivery is described as Scope management. Scope management is composed of five distinct phases: Scope initiation Scope planning Scope definition Scope verification Scope change control Scope initiation refers to the justification phase. This is when a Product management team create Market requirements and Product requirements documents … Read more
Part one – What would you like sir Part two – Requirements,tests, training, help files Part three – Why no project exists in isolation-what should be done Part four – Business rules, Process rules, Process, Data, different viewpoints Part five – Testing requirements is not optional Part six -Requirements strategy can make or break your project If … Read more
Part one – What would you like sir Part two – Requirements,tests, training, help files Part three – Why no project exists onin isolation-whwat should be done Part four – Business rules, Process rules, Process, Data, different viewpoints Part five – Testing requirements is not optional Part six -Requirements strategy can make or break your project Yes … Read more
Part one – What would you like sir Part two – Requirements,tests, training, help files Part three – Why no project exists onin isolation-what should be done Part four – Business rules, Process rules, Process, Data, different viewpoints Part five – Testing requirements is not optional Part six -Requirements strategy can make or break your project How … Read more
If you began with a vague idea and kept changing things in the hope that you would eventually end up knowing what you wanted, then success is about as easy to find as the end of a rainbow.
Really! – Have you seen this new stuff?
This could easily have been Mick Jagger and Keith Richards after their first successful gig. In the modern world, it is more likely to be a hard working CTO talking to a COO about his systems needs
To fully understand requirements it is necessary to break them down and consider each on it’s own merit. First of all requirements come from different viewpoints and these angles must be fully considered.
The key viewpoints to consider are: Business rules, Processes, Process rules, Data rules and models, Operating environment internal and external, Culture, Skills, Adaptability.
A key to building a rock solid business case is to understand the relationships between requirements, features, benefits and risks and to take a methodical approach to evaluating likely ROI as a key part of the process.
There is no excerpt because this is a protected post.