Page 226 - demo
P. 226

4.0 Cisco IPT

               For many of the stakeholders, support requires signed approval, but it doesn’t stop with
               a signature. Keeping this rule also demands that you ensure the stakeholders’ ongoing
               interest in your project.

               Rule 9: Thou Must Be Willing to Change

               This rule goes along with Rule 3. You must be willing to adapt the project plan and
               implementation to guide the project where it needs to go. Sometimes things change for
               justifiable reasons, such as a rain storm that stops the work on a construction project.

               Rule 10: Thou Must Keep Others Informed of What You’re Up To

               You must keep all the relevant stakeholders informed of your progress, problems, and
               changes. The way to obey this rule is simple: communicate, communicate,
               communicate. As things change on the project (andt hey always do), you’ll find through
               your communications that the stakeholders may want or need to introduce their own
               changes into the project. You’ll have to frequently refer to Rule 9 while adhering to Rule
               10.

               Graham’s Law: “If they know nothing of what you are doing, they suspect you are doing
               nothing.”

               Rule 11: Thou Must Be Willing to Try New Things

               Because every project is different, with different people, goals, and challenges involved,
               it would simply be inappropriate to use the exact same methods, software, charts,
               graphs, or other aids on every project. The standard methods and tools can be used
               with all projects, but not all projects involve the same risk or complexity. Large, complex
               projects will likely use more methods or tools than smaller projects. Both too many
               methods and too few tools can doom a project. You must adapt the processes,
               technologies, tools, and techniques to the needs of the project at hand.

               For example, you obviously need to put more detail into the network diagram for
               building a new corporate headquarters from scratch than you would for setting up a new
               sales office in a rented building. And some recurring projects, such as managing the
               monthly production of a newsletter, might not need a network diagram at all.







               Technical Manual
   221   222   223   224   225   226   227   228   229