The Project Management Institute (2017:138) defines Collect Requirements as the process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives. Determine the Collect Requirement: Inputs, Tools and Techniques, and Outputs of the project below.

Managing a 2-Week Project

Recently, I experienced the challenge of having short project, a 2-week project. Im called to action. Theres a new project and its got my name all over it. My face shows focus and excitement. The project starts tomorrow and runs for only two weeks.

Project Details

We had been hired to create functional prototypes for a user testing engagement. There was a finite date for this testing and it was quickly approaching. The prototypes have to take into account about six different flows and countless use cases. Like the delivery date, the budget was also fixed and finite we had to do some fancy number games to get the right team composition to ensure the success of the project.

QUICK FACTS

- Type of Client Company: Home appliance

- Type of project: Prototyping for user testing

- Cost or cost range: $20,000 $50,000

- Timeline: 2-3 weeks

- Team size: 5

- Methodology: N/A

- Main goal: Accomplish prototyping to client specifications prior to user panel testing date

- Main challenge: Getting assets needed from the client to turn around a timely prototype.

The team is quickly on boarded and the internal expectations are shaped around the unexpected and unyielding demands of a two-week project.

2-Week Project Tips: How to Manage A Short Project

1. Who comprises my team and are they armed with the tools and assets they need to at least begin work?

Given the parameters, we ended up with a team comprised of a Delivery Director, a Project Manager, an Architect and two offshore Developers. We were relying heavily on the provision of assets to base design on and this became a bit of blocker at one point, resulting in the addition of another developer for a day or two.

2. What meetings are crucial (daily standups, demos, etc.) and what can be disregarded (retros, grooming, etc.)?

We decided that daily stand ups with the client and demos were the two essentials for a project this short. Namely because the key here is staying aligned and on time. Failing at one of those would jeopardize the success of the whole project.

3. Does your team and your client have a thorough understanding of what is being developed and delivered? Is there complete alignment?

Thanks to the meetings mentioned, our continued touchpoints ensure alignment through delivery.

4. What does the full timeline of this project look like? When are check-in points, QA, revisions?

The timeline was established going into it but had to remain very flexible. There were quite a few last minute lets jump on a call meetings to clarify issues and defects that arose during development.

5. Does this lead to another SOW that expands on this portion?

In our case, it doesnt, but more similar work will be granted to us in the future as these prototypes are needed.

HELPFUL TIPS

At the very start of the project, establish a real-time method of communication with the client. This type of deadline will require immediate response to questions and the standard respectable delay will not suffice.

It will be very important to allow key players the time needed to actually do the work. Bogging them down with meetings is going to risk your ability to deliver on time. Keep the workers working and be diligent about relaying information as needed.

TALK TO YOUR TEAM! Keep a constant pulse on what they need, how its going and any and all possible blockers. This goes for any project but is especially important for one that is so short-lived.

In the end, youre the digital project manager and it is your job to deliver a successful project to your client.