Search Bloguru posts

Tai: Diary

Blog Thread

  • PRINCE2 Agile behaviors 2

PRINCE2 Agile behaviors 2

PRINCE2 Agileは、プロジェクトの初期段階から計画に取り入れます。真価を発揮するのは、成果物を出すタイミングです。一般に、Agile自体がそういうもののようで、プロジェクト管理とは異なる階層にあります。トラブルを起こさないよう、上手く調整するためのノウハウです(教科書では、フレームワークと書かれている)。ITIL 4のコンセプトに近いと思います。尚、Scrumというフレームワークがありますが、Agileの一形態に過ぎないようです。

  1. Transparency
    The most important elements of this principle come in the form of the common agile values of honesty, trust, integrity and respect. Transparency means that everyone knows the situation and there are no surprises.

  2. Collaboration
    A motivated and respectful team is greater than the sum of its parts if people work together and provide cover for one another. More can be achieved this way than working in silos. An example of collaboration could be where a team is falling behind with work due to one person having difficulties with a technical problem. One person on the team is ahead of schedule on their own work, so they stop to help the colleague.

  3. Rich communication
    People should always use the most effective channel to communicate. Using face-to-face and/or visualization are many times faster and more effective than words on their own. A rich communication environment should be created, allowing information to pass freely in a culture of commitment and trust. There is still need for documentation, but by using other more effective channels, it can be replaced or complemented and greatly reduced.

  4. Self-organization
    The people closest to the work will usually know best how to get the job done. Therefore people should be trusted to do it. Self-organizing creates mutual respect. A project manager can leave a team manager to focus on product delivery, thereby making team manager feel trusted. This principle extends far beyond the work.

  5. Exploration
    Frequent question and rapid feedback loops in any form provide an opportunity to learn. Learning helps to improve the products. By continually working in loops that deliver something and create feedback, the team can go forward. The shorter these feedback loops are, the quicker progress can be made and the smaller will be the impact of any mistakes.


People Who Wowed This Post

  • If you are a bloguru member, please login.
  • If you are not a bloguru member, you may request a free account here:
    Request Account