Planning an initiative

As introduced in Planning from the purpose needed, with the term "scaling down", we therefore need to plan every initiative with a top-down approach, where we take both the functional and non-functional requirements into consideration to make a proper systems design, please see the page systems designed architecture for further information and details.

Since it in big systems will be many components, there will be many teams that are developing the system at the same time, where every team and their component in turn can require systems design within the component. Having many teams makes it important to have an interdependency and delivery board to keep track of all the dependencies, interdependencies and deliveries between the teams and the deliveries to outside the team of teams' constellation. Very big systems require many of these constellations to deliver, which in turn requires an interdependency and delivery board on also on the wholeness level.

A release plan is also a suitable planning tool that shows the different output from the initiative in the future, when sub-releases are possible. A visual release plan is also a terrific communication tool to management and the rest of the organization. It is the possible to be updated with what is the coming output and when from the initiative, as well as track the progress, until the final release. If release on demand is a necessity for the customers, that can also with short notice be added to the release plan.

Every level also needs to keep track of their own backlog, which can be of different kind, like; incidents, maintenance, further enhancement and completely new products (systems).