Skip to main content

Tag: Requirements

Slay the Dragon of Risky Innovation

It is well accepted that companies who embrace innovation achieve competitive advantage and prevail in difficult times…

while companies that do not innovate become less competitive and can’t survive due to their lower performance.

Even though most companies write in their vision statement something like “leading by innovation” in most cases that declaration is not much more than beautiful words. Few of them have a strategy based on innovation. Several companies are not continuously innovating, rather innovating casually and haphazardly. When they implement innovation projects, usually they suffer high stress, because their mindset is the mindset of efficiency and optimization, while innovation deals a lot with experimentation and uncertainty.

Sponsors of innovation projects are intrapreneurs; therefore they are optimistic and perseverant by nature. As a project manager, your mission is not to be optimistic nor pessimistic, but realistic. You should have the ability to identify risks and to project scenarios, and to prepare risk responses and to have contingency plans to minimize economic and productive losses in case of failure.

The change of a piece of equipment in the production line by a prototype that can produce new products or achieve superior levels of quality and productivity correspond to a typical innovation project in production lines. The sponsors of the project usually have high expectations. Vendors and manufacturers of the equipment are very optimistic too (it cannot be another way because they must sell you the equipment). In general, manufacturers have tested the equipment in their factories, but factories conditions differ in much aspects to the environment in which the equipment should work.

Innovation, by nature, implies risk. You should realize that success is just a possibility, not a particular result. Other possibilities are a partial success (or partial failure) and total failure. Eventually, goals will be achieved, but rarely on the first try. Innovation implies iteration.
Some problems that can be present during commissioning of a prototype productive machine are:

  1. Product specifications not achieved.
  2. Specified productivity or quality rates not achieved.
  3. Excessive time in the adjustment or calibration process.
  4. Erratic or unstable performance.

The impossibility to achieve product specifications and productivity or quality rates could be related to poor product specification during the design phase (possibly the equipment was designed to process a limited number of products, not the entire set produced in plant), poor raw material specification, incorrect design or lack of quality in the components or in the construction of the equipment.

Excessive time in the adjustment process and unstable performance could be related to poor design, insufficient testing of the prototype in the factory and uncontrolled variables like work environmental factors, variability in raw materials, etc.

If the calibration of the equipment takes several times the scheduled time with no significant improvements, it is time to realize that the problem is not adjustment but the design and go back to the engineering office to improve the design. Ideally, define with anticipation how much time will be available for changes, avoiding unsuccessful work and time.

While various of these causes could be prevented during the design or engineering phase, as a project manager, you must be prepared to confront these issues during the commissioning phase.

Some important questions to consider during planning risk responses are:

  • Is the modification reversible?
  • Can we produce and stock a considerable amount of product before that the replacement of the existing equipment is done, to replace the lack of production during the commissioning phase of the new equipment?
  • In this case, what volume or quantity of production is necessary?
  • There are other equipment or lines in the plant that, working at high production rates or in additional shifts, can compensate the production of the replaced equipment during the commissioning process?
  • If we are not able to achieve to produce an individual product, what percentage of the production volume it represents?

The answer to these questions involves the engagement of several areas, like production planning, operations management, logistics, sales, etc. In some cases, it could be convenient to communicate the project goals to the clients, and by that way, get some flexibility from them, in view that the project will result in a better quality of the product or in better order completion time.

Finally, during the commissioning process, you must manage stakeholder’s expectations and moods. When things do not work as expected, frustration, rage, and discouragement appear. If you have developed scenario analysis and alternative plans, and you have communicated risks before the execution phase, you are in good standing.

The Project Mindset – Fact or Fiction?

I have been thinking about this project management topic for many years. Is the Project Mindset real?

Is there a culture or a set of habits or behaviors that can define the Project Mindset? Do Project Managers have a Project Mindset?

What makes some people more suited to projects than others?

What are the traits to look for when selecting a team for a project that may not necessarily have direct project experience?

What can essential knowledge sharing do so that the team members are clear on the project culture?

This scenario is becoming more relevant as operational staff in many organizations are increasingly expected to work on projects as they have intimate knowledge of the business processes impacted. Although operational targets are similar – they tend to be repeated, so the team knows how to achieve and repeat them.

The Project

When we look at a project in general and key elements of a project, here are some of the ways in which a Project can differ from an operational environment.

  • A Project Has a Beginning. It is not a pre-existing entity.
  • A Project Has an End. Once the scope is delivered, the project will finish.
  • A Project is a Temporary State – it will not continue forever. Project teams, Rooms and Ways of Working are temporary.
  • A Project is Unique. Even if the delivery of a project is part of a wider program, the project is unique to its team, site, and installation. A project is not repeated.
  • A Project is Not Part of Business as Usual. Projects are not defined operational processes and tasks which are easily repeatable.

Project Resources

Looking at the above features. The First two items, i.e. the Project has a beginning, and the Project has an end is obvious to most people and needs no explanation or introduction.

The other three elements Temporary State, Unique and Not Part of Business as Usual create some of the biggest challenges for Operations or Support teams that are suddenly thrust into projects or find themselves on a project team.

Operations and Support teams are used to a routine. Each week looks and feels that same, standard work practices, standard tasks and a fixed meeting schedule for each week.

A Project pace of activity will vary as it moves from Kick off to Specification, Design to Build, Build to Test, Test to Qualification, Qualification to Implementation and Implementation to project close.

With each of these project phases comes a different challenge, a different pace and the ability of the project resources to adjust. The pace and change to the level and type of activity are critical to the success of the project. This change of routine, pace and activity are what most operations based people can tend to struggle with for the first time they are working on a project.

Project Culture

A Project Manager or Engineer with years of experience will instinctively know when to adopt a different pace within a project whereas the operations resources will just become comfortable with varying levels of pace and change.

When the pace changes some of the resources will adapt and deliver even if they are moving out of their comfort zone. Personally, I have always encouraged people to keep learning and to move out of their comfort zone from time to time as this experience will promote the individual growth.

As Project Managers and Project Leaders should we avoid or to address the aforementioned comfort zone? Is prevention better than cure? If a resource has no project experience, should we consider them for business-critical projects?

Alternatively, should we offer them advice, coaching, and support to facilitate the transition from a non-project to a project way of working? Are people capable of adopting the “Project Mindset?” This is an opportunity for you to develop as a leader by coaching someone into a position of confidence in their new role.

Team Selection

When selecting Operations based resources for projects consider the factors above. Is the person suited to a change of pace, change of activity, or change of routine? Directly asking the person may not yield the correct answer. You need to do a little research on the individuals as you would when recruiting for any role.

Find out if they have a track record of adopting change into their daily work. What has their past response to new company policies, procedures, processes, and systems? How have they responded to pressure situations in the past or to last-minute changes of direction?

You need to do your research when hiring project resources for several reasons, but above everything else the biggest constraint is time. As projects have a fixed planned duration, you may not have the time to take a risk on a resource.

In Summary

Moving from operations to project based work should be seen as an opportunity to grow as an individual and expand the capability of the person and the organization.

There no hard and fast rules to selecting project resources but I look for the “Project Mindset.” I define this as a set of characteristics that will provide an indication of how a person will respond to a project.

How I summarize this is:

  1. The ability to cope positively with change
  2. A willingness to dig deep to complete a milestone
  3. Does not tend to knee-jerk react to surprises encountered on a project
  4. The Capability to move roles and work multiple roles to get the job done
  5. The ability to switch off and chill after a period of high-intensity working
  6. Must not take any work-related discussions personally
  7. Can keep focused on the end goal
  8. Believe the end goal is possible
  9. Can support the team to deliver the scope at all costs

Sounds easy, yes? I would love to know your thoughts on this topic.

Worldwide Advice from Successful Project Managers

Project Managers are responsible for the implementation of project tasks within the prescribed terms, and using existing resources.

The project manager builds a development plan, organizes a team, establishes the processes of working on a project which control the quality and delivery of products in time, and more. Several world class project managers shared their recommendations* for the sake of novices in this field. In this article, you will find useful rules and approaches that successful project managers apply in their work.

Always Be Composed

Remember that nobody will respect a flustered team leader. Try to always remain calm and collected in any situation. Plan your work and follow it. During the execution always work on your most complex pieces of work or sites first. If you do this, you will have a sufficient time for recovery, if required. Make use of task managers, world time clock, and programs for better productivity.
– Julie Craig, Melbourne, Australia

Build Trust

When you communicate with your team, listen to them attentively, making sure that their understanding and expectations are clear and precise. Build trust, support your team and respect their points of view, even if you fundamentally disagree with them. If you do not have faith in your team members’ skills, you cannot fully rely on them, and vice versa. If you plan to implement many successful projects, you need to learn how to build an open relationship of trust.

Think thoroughly, seek input, make decisions and act. Be flexible – don’t be afraid to make mistakes, but be ready to correct and change them.

– Hammad Khan, San Francisco Bay Area, USA

Discuss the Risks and Challenges

  1. No surprises. Make sure that key stakeholders are told about issues and risks before they are raised at meetings. Tell them what the possible options are for resolving or mitigating them and what you recommend. However, make it clear that it is their call. In this case, they will have time to reflect and decide – often choosing the option that you have suggested.
  2. Proper planning. You should have a proper plan with milestones, dependencies, durations, resources to do your job successfully. You will need appropriate information as you move up the stakeholder chain. Usually Chief Executives want a detailed picture on one page with key milestones and indicative dates – not the whole plan, but they must have it if it is needed.
  3. Governance. Successful project management is impossible without a fully constituted, regular and well-attended Steering Committee, which makes decisions and supports you. A proper project hierarchy includes having all the key roles identified and filled with agreed job descriptions. Also, there should be an internal project meeting structure with weekly or daily one-to-one sessions as appropriate and an up-to-date Escalation Matrix so that everyone knows who to contact when things go wrong.

– Chris Clegg, Kempshott, United Kingdom

Ask Questions Constantly

Keep digging and asking why. You need to know all about your project – planning features, objectives and results of the tasks as well as a monitoring plan, which identifies key performance indicators and tools. Organize your work clearly; keep a tracker of all activities and tasks. Keep all Stakeholders and Team members engaged in the work and make sure the tasks that are being monitored are regularly updated.

– Anonymous Author

Keep Detailed Project Documentation

You should monitor the status of completed tasks and never stop communicating with the team. Keep detailed documentation of the project and constantly keep all the team members posted of the latest news of the project.

– Pietro Cordier, Zurich Area, Switzerland

First, Determine the Objectives

Define the project scope well and avoid assumptions as much as possible. Clear the definition of the project terms and concentrate on the stated goals.

– Serge Nalivayko, Las Vegas, USA

Develop Communication Skills

The most important quality of an effective project manager is communication skills. Communication with the team members allows us to promptly identify any inconsistencies. Interacting with customers makes it possible to quickly identify any changes in the requirements for the project.

Build motivated teams and trust them to do the job. The success or failure of your project depends on each member. Therefore, in addition to knowledge and skills, you will need the ability to effectively motivate and manage people.

Plans are alive, so always reiterate them. Collate the task’s progress with the plan. For effective risk management, you should be able to adapt quickly to any fluctuations and make changes if they needed.

– Islam Kotb Ismail, Munich Area, Germany

Adhere to Triangle of Cost, Time and Deliverables

While planning, and implementing the tasks, adhere to the Triangle: Cost, Time and Deliverables. Ensure that the stakeholders have the same frameworks.

Eliminate or Reduce Risks and Resolve Risks. To develop an effective strategy and to implement the project within the stated terms, it is necessary to constantly monitor the risks that may arise during the project, and to have at hand a plan to reduce risks.

Work hard and persevere with every task. You cannot know everything but take every opportunity to acquire new knowledge.

– Christo Farmer, Cape Town Area, South Africa

Honesty, Flexibility, Consistency

Consistency in the team is the key to success. Keep trustful and honest relations with clients and colleagues. Promise less than you can, but do more than promised. Regularly develop new skills and be flexible in the choice of methods used in project management.

– Andrew Soswa, Greater Chicago Area, USA

Prioritize the Project’s Tasks

Communication is never over. Communicate to quickly identify any changes and issues.

Have daily planning, assessment, and prioritization. Coordinate your priorities, distribute power and responsibilities among the project participants and achieve project implementation.

Get as much knowledgeable experience and expertise as possible. Experience is the most valuable resource of effective project managers, which comes only with years of hard work, mistakes and the invaluable advice of mentors.

– Robert Hunt, Greater Minneapolis-St. Paul Area, USA

Impugn the Ideas to Make Them Better

Your task is to manage projects effectively. Your team’s task is to provide the necessary knowledge and experience. Therefore, it is often useful to ask for clarification of what you are told. If you don’t have the necessary technical knowledge base, ask the technical experts to explain their proposed solutions to ensure their validity and effectiveness.

– Scott Larnet, Kuala Lumpur, Malaysia

Be Creative

The key quality of a successful project manager is the ability to interact, troubleshoot problems and make decisions. Think innovatively and outside the template, but keep in mind the strategic picture of the whole project.

– Melanie Williams, London, England

Keep Team Proposals and Ideas on Track

During the meeting, it is important to stay focused and direct the discussion back on track. Note the ideas, requirements, comments and problems of the participants; try to divide them into categories for practical implementation. Thus, you will be able to focus the participants’ attention on specific agenda items, and assign responsibilities effectively.

– Michael Hammud, Greater Chicago Area, USA

Want to Share Your Tips?

Share with us your suggestions and ideas in the comments below. Tell us your rules for successful project management and the software you use in your work.

Editor’s Note: Some quotes and statements were edited from their original form for readability.

OUTSIDE THE BOX Forum: A Higher Order View of Project Management

Project managers have been fixated on the PMBOK. The number of PMPs and the popularity of training programs to help project managers pass the certification exam is testimony…

but PMBOK is only a small but necessary part of this story. Open your mind to the following possibility.

In the complex project landscape, the most effective project management approaches will be ones that are flexible, and that will be determined by:

  • the characteristics of the project
  • the organizational environment
  • the external market situation

All three of these are dynamic, and when any one of them changes, the project management approach might also change. The objective will always be to maintain the alignment of the project management approach to the project in order to achieve maximum business value and minimization of the risk of project failure. In other words, projects are unique and so should the best fit model for managing them also be unique. That is suggestive of a higher order view of projects and project management that has not been developed by the project management thought leaders. That is, not until the business model introduced here came to be.

The Characteristics of the Project

That higher order view of projects is a four-quadrant landscape of project types as shown below.

wysocki 040617 1

Figure 1: The Complex Project Landscape
These four quadrants define projects that are very different and that require very different management approaches. But know that these approaches will draw heavily on the 5 Process Groups and 10 Knowledge Areas of the PMBOK.

  • Traditional Projects
    For these projects, both the goal and solution are clearly known and completely defined at the outset. A WBS and project schedule can be developed and used to manage the project effectively. Few changes are expected. Life could not be simpler.
  • Agile Projects
    For these projects, the goal is clearly known and completely defined but how to achieve it (the solution) may be almost completely known, partially known, or hardly known at all. A WBS can’t be generated nor can a project schedule. These projects are managed in iterations where each iteration is designed to learn and discover missing pieces of the solution. Hopefully, all the missing pieces can be discovered before the time or budget runs out. These a higher risk than the Traditional Projects and an acceptable solution may not be found.
  • Extreme projects
    For these projects, neither the goal nor its solution is clearly known at the outset. R&D projects are usually typical of these projects. These projects are also managed in iterations where each iteration is designed to learn more about the goal and possible solutions. The results usually reduce the scope of the goal and identify possible solution paths for the updated goal. In the end, the goal and solution converge.
  • Emertxe Projects
    For these projects, a solution to some problem exists at the outset, but the goal to which they align is not clearly known. The project is done in iterations where each iteration is an attempt to discover or define the goal. The resulting deliverable goal may or may not have business value.

The big question is where does your project fall in these four quadrants?

The Organizational Environment

Management can entertain all sorts of new business opportunities, and envision processes and practices that work perfectly. Someone has to pay attention to the ability of the enterprise to deliver on these dreams. In most organizations, human resource capacity, among all other resources, usually happens by accident rather than as the result of a human resource management system that aligns resources with the strategic plan of the organization.

Market opportunities can only be exploited within the capacity of the enterprise to support them. Two of the big questions for senior management is how to spend current enterprise resources for maximum business value, and how to grow those resources to align with future strategic portfolios.

Enterprise capacity is both a constraining factor and an enabling factor. As a constraining factor, what the enterprise should do is limited by what the enterprise can do in the near term, and finally, leads to what the enterprise will do. As a counter measure to the constraining factor, the enterprise needs to assure the alignment of not only resource supply but also resource availability against the business demands for those resources. So enterprise capacity is a dynamic tool that can be adjusted as a deliverable from the planning exercises. Expanding or enhancing resources will reduce the schedule contention between resources, but that is a business decision that arises during the fulfillment of the strategic plan.

As an enabling factor, resource managers collaborate with functional business managers and line of business (LOB) managers to creatively solve resource availability problems and enable the exploitation of new business opportunities. These collaborative efforts result in the commissioning, scope revision, rescheduling, postponement, and termination of projects, programs, and portfolios. This is the reality imposed by the ECPM. We have no choice but to deal with it!

The External Market Situation

The feeding frenzy that has arisen from the relentless advances of technology and the Internet has had several disruptive effects on the business climate. These effects are global and have unknowingly put many businesses in harm’s way. The Internet is the gateway for anyone, anywhere to create and sell their products and services! Business sustainability now depends on how effective a business can erect barriers to entry for new competitors, and how it can “out create and outpace” the competition. Anyone, regardless of their physical location, can be a competitor. Even if you don’t sell in the international markets, your competitors can and do, so you are pulled into the global marketplace and may not even be aware of it. Your business decisions must consider actual and potential global impact.

Market opportunities will come and go, and not on a schedule that organizations can predict or even be able to accommodate. Whatever project environment your organization embraces, it must be able to respond immediately. The opportunities can be internal (problem-solving and process improvement to maintain or improve market position, for example) and external (new product, service, and processes for meeting the needs of an expanded customer base, for example).

The Higher Order View of Project Management

That higher order view of project management is captured in the 3-phase model:

  • Ideation Phase
    • What business situation is being addressed?
    • What do you need to do?
    • What will you do?
  • Set-up Phase
    • How will you do it?
  • Execution Phase
    • How will you know you did it?
    • How well did you do?

Embedded in the Ideation Phase are such activities as Brainstorming, Business Cases, and Requirements Elicitation. Embedded in the Set-Up Phase is PMBOK and the portfolio of project management life cycle (PMLC) models to which it applies (Traditional, Waterfall, Incremental, Prototyping, Scrum, FDD, PRINCE2, DSDM, etc., etc.). Embedded in the Execution Phase are 5 processes: Define, Plan, Build, Monitor Control and Close.

The ECPM Framework that drives all of this is shown below in Figure 2.

wysocki 040617 2

Figure 2: The ECPM Framework

The Why What and When of a Decision Log

Can you relate to that project that feels like it has been dragging on a little too long?

Moreover, your team is sitting in a conference room drowsy from preparing the final touches when one perky creative soul, who by the way missed the first four months of meetings (thus why they are perky), pops up with a question ‘Why are we doing it this way? We should look at a different option?’

Hallman 012517Once the collective groans subside, everyone starts in on a chatter contemplating a different option. “Wait,” you think, “it has already been hashed out!” Quick, where are your notes? Where is that email talking about a different option? Was it in the meeting minutes somewhere? “When was that again? February?” This is all too familiar. You can’t quickly find the results, and you desperately want to stop all of the cross-conversation and new found excitement that has roused up the room. Then you sit back and remember, “Ah yes, I have a decision log!” You swiftly scan it, find the related item and pound your gavel on the table to gain everyone’s attention. It will all be fine, we are on the right track, and we don’t need to spend another moment of discussion because it was already agreed which would be the best action. Phew!

Utilizing a Decision Log, which is a list of critical decisions agreed upon throughout the project, has not yet leaped into mainstream project management practice, although it has started to gain traction being viewed as beneficial for recording impactful decisions and serving as a central repository for those decisions.

Why Do It?

The concept is a simple one. Once a discussion begins regarding a project, decisions are being made with some decisions essential for the direction of the project. Documenting those in a central location can be of value throughout the project as a quick reference and communication tool to assure everyone is aware of the direction.

Decisions may not always be agreed upon by the team members. Rather than opening a discussion for debate each time the topic arises, it is better to resort to the documented decision and move on from the topic.

Additionally, these decisions may be made in a forum that does not involve all team members, and they may be hidden in meeting minutes or informal email messages. Providing a standard method to document and communicate decisions can assure everyone is aware, avoid lack of clarification, and can be used as a method to focus team members when debate arises.

Decisions can be revisited when necessary, and may even be changed when new information presents to the project. Team members who raise valid points that counter a decision should be heard and their opinion valued as it may offer a better course of action.

What Information to Include?hallman 2 012517.jpg

A decision log is a beneficial communication tool to assure all stakeholders are apprised of how a decision was reached, what other options were considered, and who is accountable for the decision. It provides guidance to the team members and can eliminate potential confusion. The format you use may be a spreadsheet, automated log, or another method that suits your environment.

The primary information to capture includes What is the decision, When was it made, Why it was made, and Who made it. Other information may be captured as well and may vary based on the project needs.

When to Include a Decision?

When to include an item in the log involves striking a balance between what is valuable to have recorded versus what is too detailed, and will take thought. As well as considering the overall audience, team members and project dynamics also consider these things:

  • Topics that are frequently debated or where there is often disagreement.
  • Decisions that may be confusing or not clear to all stakeholders.
  • Those made that impact the direction or future work of the project.
  • When alternatives exist, but only one must be selected.
  • Decisions made by leaders, or others outside of the project team, which will impact the work of those team members.
  • Those that impact what or how a deliverable will be achieved where it may be different than some stakeholders expect.
  • Items that may not seem significant but can cause issues if not understood.

As a project manager, you must judge what your stakeholders will view as too much detail. You also must consider not eliminating items that you think are valuable to minimize detail.

There you have it!

No one wants more documentation. That goes for the individual who must create and maintain it as well as the recipients who do not want yet another attachment to read. The value of the log is for the project manager to have a centralized location to capture items that may cause debate or slow progress or for those who are included to search for information on the project materials instead of hunting down the project manager. This can turn into a time-saver and worth a try it on your next endeavor!