by Francois Coetzee
Creating business models that are easy to understand are invaluable tools for understanding the inner workings of the organization, its functions, its role players and the business entities it uses, creates and consumes. It is a critical foundation for the system models that describe the supporting software architecture and allows for easy trace-ability and impact assessments of business to system and system to business. Using the simple approach described in this article will allow the business modeller to rapidly create accurate business models.
Serious games are games whose primary purpose is not entertainment. Cooperative games structure communication (e.g. contract bridge) and cooperation (e.g. soccer) between players in the same group.
Using serious, cooperative games improves Requirements Understanding (RU). This paper defines six RU games, maps them into ‘initial understanding space’, and shows how to use a special Ouija board to choose the games to play on your project. An example of RU game selection is included.
I hope this forum can help me.
I’ve written a functional specification for an enhancement to the system across the full business horizontal – new procurement, new storage, maintenance, new products, and five distribution channels.
All the business stakeholders have signed-off the specification +/- 20 people, with the exception of four signatories from IT, who will program the solution.
IT has sent the spec back four times for what I regard as relatively minor changes. I get the impression that the individuals there are being obstructionist. It’s starting to cause serious delays on this project.
Does anyone else have any advice about how I can get an obstructionist IT team to change to work with us rather than against us?