This activity is part of the Cycle Planning. Each cycle is a month, and starts by detailing the high-level plan created in the Preparation for the upcoming month. This section shouldn't take more than 3 days.
Send a message to everyone, and tell them about the expected achievements in the upcoming month, and the risks involved, as well as planned responses to those risks. It’s important to let everyone know their role in the overall achievements of the project, and ensure they are aligned with the goals, rather than focused on isolated specialist activities.
- Hi everyone,
We’re going to start the next cycle for ProjectXYZ.
First, I have to thank Mary for bringing up the risk of new regulation, and all of you for helping find the best response to it.
Based on the planned response, and our project schedule, we really need to complete the three main features of the backend during this cycle, and submit it for approval; otherwise everything will be uncertain in the project.
If you had any questions about those features, the best person who can help you is Michael.
- Hi everyone,
We’re starting a new cycle in ProjectABC. Unfortunately, we’re two months behind schedule, and it’s getting serious. What we need to do is to reduce this to about 6 weeks until the end of this month, and the best way to do it is to focus most of our effort on resolving the conflicts between utility and structural designs, and get their approval. So, I’d like to ask all team members involved in construction to give priority to helping their peers in the headquarter, especially by providing their hands-on experience in the project.