Project Management and Agile: Run Projects That Ship

Most projects do not fail because people are lazy. They fail because nobody agreed what could bend and what could not. When trouble comes, the team argues instead of acting. A short ranking made on day one settles those arguments before they start.

This course walks you through building one full plan, called the Project Plan Pack. Each module adds pieces to it. By the end you will hold a complete plan for a real project of your own.

Every lesson has the same six parts: what you will be able to do, why it matters, the teaching, a worked example, common mistakes and a check that you are done. Read the example, then do the task on your own project and save the result in your Pack. Modules 2 to 6 open with three review questions from earlier modules, and the workbook holds templates you can copy. This course teaches concepts and skills only. It is not tied to any exam.

A project is a temporary effort to create something new. That something can be a product, a service or a result. A project has a start, an end and a goal. Routine work is different. It repeats and never really ends, like paying bills or answering daily email.

Ask three quick questions about any piece of work:

1. Does it have an end date or an end result?
2. Will it create something that did not exist before?
3. Will the effort stop once the goal is met?

Three yes answers mean you have a project. Project management is the set of planning and tracking habits that help you reach the goal with the time, money and people you have.

Every project has three limits. People often call them the triple constraint.

• Scope is everything the project will deliver, and nothing more.
• Time is when the work must be finished.
• Cost is the money and effort you can spend.

The limits pull on each other. Add scope and you need more time or money. Cut the time and you need less scope or more money. If you squeeze all three, quality drops or risk rises. Quality and risk are not limits you set. They are what gives way when the limits are too tight.

To rank the limits, give each one a different label:

• Fixed: it cannot move.
• Firm: it can move only for a strong reason, and with approval.
• Flexible: it is the first to bend when trouble comes.

You cannot label all three fixed. Then nothing has room to bend, and the plan breaks at the first surprise.

Pick your course project. Choose something real that you can influence. Aim for a clear end and a few weeks or months of work. Good examples are a small event, a product or service launch, a home or office move, a website, a workshop or a fundraiser. You will plan this project through every module.

Example (illustrative numbers): Maya runs Juniper Lane Candles, a small shop. She wants to launch three new autumn scents at a market stall on a set Saturday. She also wants a simple web page that takes orders. This is the running project for the whole course.

She asks the three questions. It ends on launch day. It creates new candles and a new order page. Making candles every week is routine work, but this launch is a project.

Maya ranks the limits:

Now the rule for trouble is clear. If work runs late, she trims scope first. Then she asks whether the budget can stretch. She never moves the date.

• Calling routine work a project. The word sounds important. Fix: if the work never ends, use a checklist or a routine instead.
• Making everything fixed. People fear saying flexible. Fix: choose one flexible limit before you start.
• Choosing a project too big. Big dreams are exciting. Fix: pick something you can finish, with a start and an end you can name.
• Ranking limits in your head only. It feels obvious. Fix: write the ranking down and share it with your sponsor.

You have chosen one real project and written it in a single sentence. You have labeled scope, time and cost as fixed, firm and flexible, with a one-line reason for each. Both are saved on page one of a file called Project Plan Pack.