In any large company, hundreds of initiatives are launched every year, each of them has a different priority and number of customers. How does an initiative launch look like? Usually, management gives a glimpse of a strategic vision and sets very high-level goals to their IT teams. Afterwards, someone from the middle-management is involved, who spends several months on prioritization, searching for internal resources. But time flies quickly and the first reporting milestones are getting closer. Realizing this, additional resources are attracted, who very often don’t have any experience in the relevant subject area. As a result, business requirements may not have any in-depth analysis, the unreal promises could be made. What will the results be in this case? How will it affect the project and how much funding will be wasted?
The client set high-level goals for the technical teams, but they are not sure how to proceed. Whose task is it to decompose the high-level goals to actionable items? The project is moving forward, and the context is constantly changing. What was important yesterday becomes secondary today. Unfortunately, the requirements change as well after approval. What is the solution?