Month: March 2019

The holy trinity of projects

Every project has a

  • Scope,
  • Budget and
  • Timeline.

This is what differentiates them from routine/regular business. Project management literature calls this trinity ‘the triple constraints”.

This trio also serves as a success measure. Truly successful projects deliver what is required, within the budget and on time.

I also believe the Trinity is in good company when Quality and Integrity butt in.

Some trade-offs might be necessary between the scope, budget and time. If the sponsor or client want a closer launch date of the product/service, additional resources and reduced scope might be necessary.

Sometimes, the project manager will have to have the courage to say No to trade offs. Saying No at the right time to anything which risks creating a scope creep is a project’s manager duty. It can be No during the design phase, before the commitment. It can be No during the implementation phase, when the client’s appetite increases. This requires some business acumen.

In the business world, some use the “law of two-thirds” to decide the trade-offs. It offers criteria for decisions about what will define a product or organization (inspired by Tyler Kleeberger, A Technique for Deciding When to Say No, Medium, published on Medium, January 2019). Essentially, you can’t do everything so what should you do?  It will not surprise you that the three criteria are (again):

  • Quality
  • Speed
  • Price

You must consider all three, but you can only choose two. For example, a manufacturer wants to deliver quality and wants to be fast? Then the products are likely going to be more expensive. A business desires to offer its services at low prices, but also wants to maintain quality? Then, it is likely that the speed is going to be reduced. Those who want something that is fast and cheap, will have to compromise on quality.

It will be important to keep an eye on the perspective and the short, medium and long-term benefits, along with a good risks management strategy. I would never compromise on integrity though.

It takes humility, strength, and fortitude to acknowledge your project’s, your team’s and your own limits. It also takes visions and leadership to choose and to focus on priorities. It is not unusual for me to ask my colleagues and my client: “So what are the 3 big things this project shall deliver?”.

IMG_1374image credit StamfordGlobal, 2008.

 

 

Advertisements

Re-post: Beyond Best Practices: How to Use Design Thinking in Rule of Law Promotion

This article “Beyond Best Practices: How to Use Design Thinking in Rule of Law Promotion”, by Siddharth Peter de Souza for PeaceLab touches upon the How and Why of the design thinking in rule of law projects (and not only, I would say): listen to what users’ say, do and aspire to and strive to meet their needs.

The ideas are central in human – centered development management theory and practice.

Link to article: https://peacelab.blog/2019/03/beyond-best-practices-how-to-use-design-thinking

Stakeholders analysis or who else is in the sandbox?

Projects are not stand-alone “enterprises”. They usually need to co-exist and be implanted in already “populated” areas by those who have /can have a stake in a project.

A project’s needs assessment or design phase shall include the stakeholders analysis. There are many ways and tools to do a stakeholders analysis, out there in literature and internet.

Why do a stakeholders analysis? This analysis enables an up-to-date picture of stakeholders’ roles and interests in the project. These can range from ministries, parliaments, local authorities, institutions and organisations, both public and civil, professional and non-professional groups, to people and groups of people.

I sometimes, make an analogy with the sandbox and start by looking around who else is in the “sandbox” and what they do. Who builds a castle (ambitious ones), who destroys it (opposition), who digs ditches (planners), who is well equipped with buckets and shovels (the doers), who sits on the edges (the expectants) …Sandbox-Pic

In development management projects, I find it useful to use the following classification of stakeholders for the analysis of their impact/potential impact on the project.

  1. Resource Providers: those who provide funds.
  2. Target Group: are directly affected by the project and directly benefiting from the work of the project
  3. Beneficiaries: those who directly/indirectly benefit, in the longer term, from the improved capacity (skills, knowledge, etc.) and quality of services and products of the target groups
  4. Project partners/supporters: provide support for the implementation of the project. Although not in B and C categories above, their co-operation is vital for the successful implementation of the project (e.g. ministries, other governmental agencies, NGOs)
  5. Potentially affected/threatened: are/could be adversely affected by the implementation of the project
  6. Opposers: are/could be opposed to the implementation of the project
  7. Undecided: stakeholders with unclear role.

These categories are not static and stakeholders might switch roles throughout project implementation. It is thus important to regularly monitor their roles and stance.

Feel free to download and use this template PROJECTS STAKEHOLDERS ANALYSIS TEMPLATE_web

 

Thought of the week: context matters

All good project managers know that context is important – he/she will not rely on a “one-size–fits-all” approach.

I am personally allergic to copy-paste, in projects and beyond. I am a rather vivid learner . After all, imitation is the greatest form of flattery.

origami by Sofia, 2017