🔑Introduction to the Project Success Handbook

Welcome to the Project Success handbook, a guide for all kinds of agile teams in the world.

Introduction

What does it take to finish projects as a team? This is a convoluted question because there are many factors involved. No one can do it alone. It takes people coming together to build trust and deliver shared outcomes.

The most common struggles for teams involve alignment and expectation setting. To accomplish outcomes together, they must align and set their own expectations. They must all agree how they will work, and what kinds of work they will do.

Teams shouldn't define it all at once if they are living the agile philosophies. They should do it as they go. They should interact with each other and respond to change. They should collaborate with their stakeholders as they proceed. They should deliver working results early and often.

Agile teams are "Self-organized". This means no one sets the expectations for them. No one tells them what to do, or how to do it. Teams build their own definitions of success. They build their own expectations. They agree to their own process. They determine their own priorities together.

How does this carry out in a project where you get together to solve problems? How does it work when you the team are collectively deciding the way forward?

We've defined what it takes to succeed in any kind of team doing any kind of collective work. This handbook describes the components of project success. We break down what it takes for any kind of team to succeed in whatever they are trying to achieve together.

Outcomes

By the end of the handbook, you will understand the following:

1. What are the components of team-based problem solving?

2. What does it take to succeed together?

3. What types of projects does this community take on, and what do they involve?

4. What kind of work do different types of projects involve?

5. What steps must take place to finish project work as a team?

Head to the Next Lesson