1. Individuals and interactions over processes and tools 2. Working software over comprehensive documentation 3. Customer collaboration over contract negotiation 4. Responding to change over following a plan
1/10
People often reference the four values without considering the introduction, but it’s important to establish a philosophy of constant change and improvement as well as generosity:
"We are uncovering better ways of developing software by doing it and helping others do it."
2/10
What does the Agile Manifesto's introduction mean? Basically, to be agile is to be perpetually dissatisfied.
Sharing learnings is crucial to any agile project. If you have a lot of unchanged processes, you probably haven’t been “uncovering better ways.”
3/10
Before we dig into the values, let’s skip to the bit at the end, where the Agile Manifesto tells us how to read them correctly:
"That is, while there is value in the items on the right, we value the items on the left more."
Now let's review the 4 Agile Manifesto values:
4/10
1. "Individuals and interactions over processes and tools"
What it means: Processes & tools are good, but individuals & their interactions are even more important.
To be agile means to be all-in on people. The authors knew that people matter & collaboration is essential.
5/10
2. "Working software over comprehensive documentation"
What it means: Documentation is good, but delivering working software is even more important.
In other words, a product with no documentation is preferable to having documentation and no product.
6/10
3. "Customer collaboration over contract negotiation"
What it means: Business commitments are good, but the voice of the customer should come first.
Contract negotiation refers to any agreements involved in the work, internally or externally.
7/10
4. "Responding to change over following a plan"
To quote former US president Eisenhower, “Plans are nothing; planning is everything.”
The point is that plans are good to work on, but they should always account for uncertainty. Plans are only as good as they are flexible.
8/10
To summarize the four Agile Manifesto values:
• The preamble encourages continuous improvement
• No. 1 places people at the center
• No. 2 focuses on solutions rather than documentation
• No. 3 promotes building the right thing
• No. 4 is about responding to change
9/10
Is the Agile Manifesto still relevant today? Not only is it relevant, but many industries outside of software development have adopted it. Simply tweaking a few references to “software” has helped marketing, HR & many other teams deliver valuable outcomes more efficiently.
10/10
• • •
Missing some Tweet in this thread? You can try to
force a refresh
The product lifecycle constantly evolves. Keeping everyone informed w/ a product roadmap is critical to getting the 360-degree buy-in you need to position your product for long-term success.
A product roadmap is a shared, living document that outlines the vision & direction of your product throughout its lifecycle. It articulates what you are building & why. It also lays out a strategy for delivering value & serves as a plan for executing this product strategy.
2/13
It’s the product manager’s responsibility to build & manage a live roadmap that is fluid & resilient. They must convince stakeholders why the investment makes sense, obtain buy-in from inside & outside the org, set expectations, & generate excitement about what’s to come.
The purpose of the daily standup is to inspect the progress being made toward the sprint goal and to adapt the work where necessary.
This ensures that the team’s work and progress is visible to all team members and provides a regular feedback loop for the team.
2/14
Effective daily scrums promote collaboration and self-organization.
For PMs, this is a game changer: rather than having to liaise, track, and manage work across the team, the daily standup encourages team members to self-organize and hold each other accountable.
If you’re part of a cross-functional product team, you may have taken part in a sprint retrospective. If you’re new to #productmanagement, this guide will get you up to speed on what a sprint retro is and why it’s important
A sprint retrospective is a scrum ceremony that is held once a sprint has ended to reflect on the work that has just taken place.
The team reviews processes, ways of working, and key learnings with the aim of improving the team’s performance during subsequent sprints.
2/12
A sprint retrospective is held at the end of a sprint, before the next sprint begins. If your sprint is 2 weeks long, the sprint retro meeting might be as short as 1 hour. If you’re working on a longer sprint cycle or on a larger team, the retro might last up to 3 hours.