Dans le monde de la gestion de projet, il est crucial de bien comprendre où vous allez et comment vous allez y arriver. C'est là que le **planning de référence** entre en jeu. Il s'agit essentiellement d'un instantané du calendrier prévu de votre projet, servant de référence absolue pour mesurer votre progrès et identifier toute déviation potentielle.
**Qu'est-ce qu'un planning de référence ?**
Le planning de référence est une version fixe et figée du planning initial de votre projet. Considérez-le comme une feuille de route qui décrit toutes les tâches, leurs dépendances, leurs durées et les dates d'achèvement prévues. Il est créé au début du projet et reste inchangé sauf en cas de changements importants de la portée du projet.
**Pourquoi est-il important ?**
Le planning de référence est essentiel pour plusieurs raisons :
**Quand réinitialiser le planning de référence ?**
Bien que le planning de référence soit censé être fixe, il y a des cas où il doit être réinitialisé. Cela est généralement fait lorsque :
**Points clés à retenir :**
**En conclusion, le planning de référence est un outil fondamental dans la gestion de projet qui aide les équipes à rester organisées, concentrées et responsables. En établissant une référence claire, vous gagnez la possibilité de suivre les performances, de gérer les budgets et de communiquer efficacement les progrès tout au long du cycle de vie du projet.**
Instructions: Choose the best answer for each question.
1. What is the primary purpose of a Baseline Schedule?
a) To track actual progress against the original plan. b) To estimate the project's budget. c) To document the project's requirements. d) To outline the project's communication plan.
a) To track actual progress against the original plan.
2. Which of the following is NOT a reason to reset a Baseline Schedule?
a) A new feature is added to the project. b) A team member is assigned to a different task. c) A major delay occurs due to unforeseen circumstances. d) An approved change request alters the project scope.
b) A team member is assigned to a different task.
3. What is the relationship between the Baseline Schedule and the current schedule?
a) The Baseline Schedule is a snapshot of the current schedule at a specific point in time. b) The current schedule is a dynamic version of the Baseline Schedule, reflecting real-time progress. c) The Baseline Schedule is updated regularly to reflect the current schedule. d) The Baseline Schedule and the current schedule are the same document.
b) The current schedule is a dynamic version of the Baseline Schedule, reflecting real-time progress.
4. Which of the following should be included in a well-defined Baseline Schedule?
a) Project budget and resource allocation. b) Project risk assessment and mitigation strategies. c) Team member contact information and communication channels. d) Detailed task descriptions, durations, dependencies, and milestones.
d) Detailed task descriptions, durations, dependencies, and milestones.
5. Why is it crucial to maintain a clear separation between the Baseline Schedule and the current schedule?
a) To avoid confusion and ensure accurate performance tracking. b) To comply with project management regulations. c) To simplify communication with stakeholders. d) To facilitate budget adjustments and cost control.
a) To avoid confusion and ensure accurate performance tracking.
Scenario: You are managing a project to develop a new mobile app. The initial Baseline Schedule is created with the following tasks:
Problem: During development, you realize that the UI design requires additional features, adding an extra week to Task 1. Additionally, testing uncovers more bugs than anticipated, extending Task 3 by another week.
Exercise:
1. **Updated Baseline Schedule:** * **Task 1:** Design the user interface (UI) - 3 weeks * **Task 2:** Develop the app's core functionality - 4 weeks * **Task 3:** Test the app and fix any bugs - 3 weeks * **Task 4:** Deploy the app to the app store - 1 week 2. **Impact on Timeline:** The updated Baseline Schedule indicates a total project duration of 11 weeks (3 + 4 + 3 + 1). This is an increase of 1 week from the original timeline. 3. **Communication with Stakeholders:** * **Inform stakeholders about the changes:** Explain the reason behind the revised schedule, including the additional UI features and extended testing phase. * **Provide a revised timeline:** Share the updated Baseline Schedule with the stakeholders, highlighting the new completion date. * **Address concerns and questions:** Be prepared to answer any questions and address concerns the stakeholders may have regarding the revised timeline. * **Maintain transparency:** Keep stakeholders informed about progress and any potential further changes.
Comments