Can Project plans artificially constrain a team’s ability to iterate and self-optimize ?
What do you think ? Saving Changes...
Sort By:
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
No, because the project plans should be done based on team's input.
Iterative development is used for over 50 years and it started at the initiative of the development teams.
I asume that self optimise is in fact the self-organise attribute of Agile teams. Teams can do both, but they need to be mature and have excellent technical skills.
The main reason for teams NOT being able to use Agile, iterative and incremental development, light documentation and so on is the lack of trust mainly caused by lack of knowledge and technical skills. Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Once plans are proposed by the project team/manager and approved by the sponsor, they constitute constraints and limitations on the freedom of the team. For example if the plan includes milestones, these can only be changed after approval by the sponsor (this is called change request).
A plan is a team's promise. If you want to promise less or nothing, modify the plan. But then you might loose trust. It is a balance. Saving Changes...
It may or may not. depends on how to define plans. As Thomas said, there should be a balance. Saving Changes...
Drake SettsuProject Manager / BloggerHi, United States
A Project Plan should not constrain the team. Build your Project Schedule with the flexibility to have the ability for the team to iterate and self-optimize. Saving Changes...
Mohamed AbuelgasimProject Manager| DAL EngineeringKhartoum, Khartoum, Sudan
If the team is involved in making the project plan this should not be a problem. But the project change process should be well thought of to allow changes and optimizations happen as smoothly as possible. Saving Changes...
