Project Inputs

When a project starts, there are a number of pre-existing expectations and likely some artifacts describing these.

It is important that everyone on the team understands the starting context and the current expectations of the client.

Project inputs should be treated like imperfect artifacts, though they are very important in understanding what has been communicated to the client and what their expectations may be. Their input into your project is not as strict sets of requirements, but as one perspective on what the client may currently be expecting and what they value. The most valuable and accurate perspective is the one of the client, now, as you continually work with them.

Your job is to own delivering value to the client and to do the right thing, not to check items off of a contractual list.

Initially, you'll need to:

• connect with your team. Has the team changed from discovery?
• review all project inputs and understand the current context. How did we get here?
• understand the project's purpose and initially proposed scope
• question and ensure that we're heading in the right direction (respectfully as everyone was doing their best with the understanding they had at the time and their experience)
• break down higher-level ideas into smaller, workable pieces
• determine new valuable items to deliver and where they fit
• work with the business to prioritize/re-prioritize
• remove items that are no longer relevant or not valuable