This posting is a bit long, but I hope you will find it informative and useful in your understanding and application of Macroscope. You will, at least, see how I apply these concepts in real life!
If one begins requirements analysis by asking the question, “What are the requirements”, the answers are inevitably not about business need, but about desired features of the automated components of the solution.
This is the first in a three-part series.
“What are the requirements?” When we start by asking that question at the beginning of a systems-solution project, we easily get the wrong answers. And as a result we have a high risk of solving the wrong problem and/or missing the most valuable business opportunities for improvement.
How can we be effective at conducting unit and integration tests with an Agile Development Team?
Stating that tests are crucial to any successful solution implementation, is far from being new. Undertaking quality control is imperative for all product components. However, ensuring quality of a solution requires a testing strategy.
This posting is inspired by comments from Dave Couture - in the discussion of Viewpoints.
Macroscope embodies a very powerful principle of system ownership by the business. One of the major implications of this principle is to assign key responsibilities to the BSM role - with a supporting team drawn from the business, not from IT. And Macroscope clearly defines the ideal qualifications of the BSM - deep business knowledge, excellent relationships inside the business - and uppermost - being clearly identified as "from the business", not IT.