Tag Archives: agile

Product Manager vs Product Owner: Roles, Differences and Salaries

If you have spent time in agile or project management, you have probably come across both the product manager and product owner titles. They sound similar, they are often described in similar ways, and both are sometimes called the CEO of the product. But they are not the same role, the responsibilities differ and as it turns out, so do the salaries quite significantly.

The Salaries

Product managers earn between $272,000 and $326,000 a year, and more in high-growth environments where stock and bonus considerations come into play. Product owners earn an average of $107,000 a year in the US. Both are strong salaries, but the gap is significant and comes down to scope.

What a Product Manager Does

Sharif Mansour spent 16 years as a product manager at Atlassian, the company behind Jira. He describes the role as driving the development of a product, defining its strategy and building out its roadmap and features.

In practice that means identifying and understanding user needs, monitoring the market, developing competitive analyses and aligning those insights into a clear product vision. From there the product manager prioritizes features and capabilities to deliver on that strategy, aligning stakeholders and teams to turn it into reality.

What a Product Owner Does

The product owner role comes primarily from agile and scrum. The Scrum Guide describes the product owner as accountable for maximizing the value of the product resulting from the work of the scrum team.

In practice the responsibilities look similar to a product manager: developing and communicating the product goal, creating and prioritizing product backlog items and ensuring the team is always working on the highest-value features. The key difference is scope. A product owner typically works with one team on one product. A product manager often oversees multiple projects or multiple teams, operating more like a program manager across the product landscape. That broader scope is largely what drives the salary difference.

Both roles require a strong understanding of the user, the technology and the business. If you are closer to a single agile team, product owner is likely the more relevant path. If you are thinking about product strategy across a broader organization, product manager is the direction to explore.

– David McLachlan

You can see what people are saying about David McLachlan here: REVIEWS

Navigate to Free Project Management and Leadership Articles through the links on the right (or at the bottom if on Mobile) 

PMI PMP 35 PDUs CourseThe Ultimate PMP Project Management Prep Course (35 PDUs)
Agile Certified Practitioner (PMI-ACP 28 PDUs)The Complete PMI-ACP Course: (28 PDUs) 
PgMP Program Management CourseLearn Program Management – the PgMP Prep Course
Full PMP Exams to Pass on the First TryFour Full PMP Practice Exams (180 Qs each) to pass your PMP on the First Try!
Scrum Master Course PSMScrum Master Course (PSM)
Product Owner Course PSPOProduct Owner Course (PSPO)
Business Analyst CourseBusiness Analyst Course

Also available are my Project Management Templates – these don’t have a coupon code but they’re a great way to save 100s of hours when you’re first starting out:

50 Project Management Templates Gantt Chart Risk Matrix and more Excel50+ Project Management Templates in Excel and PowerPoint (Gantt Chart, Risk Matrix and more!)
Project Management Plan TemplatesPre-made Project Management Plan Templates: Save 100 HOURS!

 

Agile from Start to Finish: Everything You Need to Know

More than 86% of software development teams have used agile in some form. If you have been meaning to get your head around Agile here is everything you need to know, from the history through to the daily practice.

Where Agile Came From

Agile did not appear from nowhere. It traces back to the Toyota Production System and lean thinking developed decades earlier. Kanban was created at Toyota in 1953. Scrum grew from a 1986 paper called “The New New Product Development Game.” Extreme programming, feature-driven development and several other lightweight frameworks followed.

In 2001, 17 practitioners representing these different approaches came together and agreed on a shared set of values. The result was the Agile Manifesto, which prioritizes individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation and responding to change over following a plan.

Agile Roles

Three roles sit at the center of most agile teams.

The Product Owner represents the customer. They maintain the product backlog, which is a prioritized list of features to be delivered, with the highest-value item always at the top. They are one person, not a committee. They have the final say on what gets worked on next.

The scrum master is a servant leader. They help the team remove blockers, facilitate cere

monies or “events” and protect the team’s focus. They are a neutral third party in problem solving to help unblock the work.

The team does the work. In software that usually means developers, but agile applies equally to research, design and any other knowledge work.

How a Sprint (or Iteration) Works

Work is organized into iterations, typically two weeks long. Here is how one flows from start to finish.

Sprint planning kicks things off. The team selects the highest-priority user stories from the product backlog, enough to fill the sprint based on their velocity. Velocity is simply how many story points the team completed in recent sprints. If the last few averaged 25 points, the next sprint is filled to 25. This keeps the pace sustainable.

Every day the team holds a 15-minute standup around the Kanban board. Each person shares their progress and flags any blockers. The goal is to surface problems quickly so the team can swarm around them and keep moving.

During the sprint, backlog refinement happens in parallel. The three amigos (someone representing the customer, a developer and a tester) come together to break upcoming features into user stories, add acceptance criteria and estimate their size relative to each other.

At the end of the sprint, the team holds a sprint review. A real, usable increment is demonstrated to the customer. Not a presentation. Not a report. The actual thing. The customer gives feedback and the backlog is updated accordingly.

The sprint closes with a retrospective. What went well, what did not and what will improve next time. Actions are agreed and carried into the next sprint.

The 12 Agile Principles

The signatories of the Agile Manifesto later published 12 clarifying principles. They are worth knowing.

  1. Satisfy the customer through early and continuous delivery of working software.
  2. Welcome changing requirements even late in development.
  3. Deliver working software frequently, with a preference for shorter timescales.
  4. Business people and developers must work together daily.
  5. Build teams around motivated individuals and trust them.
  6. Face-to-face communication is the most efficient way to share information.
  7. Working software is the primary measure of progress.
  8. Maintain a sustainable and constant pace.
  9. Pursue technical excellence and good design continuously.
  10. Simplicity, maximizing the work not done, is essential.
  11. The best solutions emerge from self-organizing teams.
  12. At regular intervals, reflect and adjust.

Agile works because it is built around real feedback, real increments and continuous improvement. Once you understand the logic behind it, the events and the roles all start to make sense.

– David McLachlan

You can see what people are saying about David McLachlan here: REVIEWS

Navigate to Free Project Management and Leadership Articles through the links on the right (or at the bottom if on Mobile) 

PMI PMP 35 PDUs CourseThe Ultimate PMP Project Management Prep Course (35 PDUs)
Agile Certified Practitioner (PMI-ACP 21 PDUs)The Complete PMI-ACP Course: (28 PDUs) 
50 Project Management Templates Gantt Chart Risk Matrix and more Excel50+ Project Management Templates in Excel and PowerPoint (Gantt Chart, Risk Matrix and more!)
Project Management Plan TemplatesPre-made Project Management Plan Template: Save 100 HOURS!

 

The Scrum Guide: Everything You Need to Know

More than 87% of people working in agile use scrum or some part of it. Yet many teams do not fully understand where it came from or how it was intended to work. The Scrum Guide, written by Ken Schwaber and Jeff Sutherland and last updated in 2020, is the authoritative source. It is free at scrumguides.org. Here is the whole thing explained plainly.

What Is Scrum?

Scrum is a lightweight framework for solving complex problems and delivering value through adaptive solutions. It works best when you cannot know everything upfront. Rather than planning in detail for a future you cannot predict, you deliver something real, get genuine feedback and adjust. That is the core logic.

The Scrum Team

A scrum team has three roles: developers, a product owner and a scrum master. No sub-teams, no hierarchies. Ten people or fewer.

Developers deliver a usable increment every sprint. They create the sprint plan, maintain quality and hold each other accountable. The term applies to anyone doing the work, not just software engineers.

The product owner manages the product backlog: defining the product goal, ordering backlog items by priority and keeping everything visible to the whole team. One person, not a committee. Others can suggest changes but only by convincing the product owner. When organizations trust this role and give it room to operate, decisions get made faster and the product improves faster.

The scrum master is a coach who also clears the path. They help the team stay self-managing, remove blockers, escalate issues and keep events productive. They serve the team, the product owner and the broader organization.

The Artifacts

The product backlog is the single source of work for the team: an ordered list of everything needed to meet the product goal. One product goal at a time.

The sprint backlog is the set of items selected for the sprint plus the developers’ plan for delivering them. Its commitment is the sprint goal: one clear objective that keeps the team focused.

The increment is the real, usable piece of value delivered at the end of a sprint. It must meet the definition of done before it can be released. If it does not, it goes back to the backlog.

The Events

The sprint is the container for everything else. One to four weeks, fixed length. The sprint goal must not change mid-sprint. Only the product owner can cancel a sprint, and only if the goal has become obsolete.

Sprint planning kicks off the sprint (timeboxed to eight hours for a one-month sprint). The team answers three questions: why is this sprint valuable, what can be done and how will the work get done?

The daily scrum is 15 minutes, same time and place each day, for developers only. Inspect progress toward the sprint goal and adapt the plan for the next 24 hours.

The sprint review (timeboxed to four hours) is where the team presents the real increment to stakeholders. Not a recording, not a mockup. The real thing. Together they discuss what was learned and what comes next.

The sprint retrospective (timeboxed to three hours) closes the sprint. What went well, what did not and what will improve next time. The most impactful changes are acted on immediately.

Theory and Values

Scrum runs on three pillars: transparency (make the work visible), inspection (regularly examine progress) and adaptation (adjust quickly when something is off track). The longer you wait to course-correct, the harder it gets.

The five scrum values tie it together: commitment, focus, openness, respect and courage. When a team genuinely lives these, trust builds and scrum works.

Scrum is simple by design. The challenge is not understanding it. It is applying it honestly and giving the team the trust and space to do the work.

– David McLachlan

You can see what people are saying about David McLachlan here: REVIEWS

Navigate to Free Project Management and Leadership Articles through the links on the right (or at the bottom if on Mobile) 

PMI PMP 35 PDUs CourseThe Ultimate PMP Project Management Prep Course (35 PDUs)
Agile Certified Practitioner (PMI-ACP 21 PDUs)The Complete PMI-ACP Course: (28 PDUs) 
50 Project Management Templates Gantt Chart Risk Matrix and more Excel50+ Project Management Templates in Excel and PowerPoint (Gantt Chart, Risk Matrix and more!)
Project Management Plan TemplatesPre-made Project Management Plan Template: Save 100 HOURS!

 

What’s NEW in the PMI-ACP Course – 28 PDUs

Agile Certified Practitioner ACP Kanban BoardExciting Updates to the Agile Certified Practitioner (ACP) Exam: What You Need to Know

There have been some significant changes to the Agile Certified Practitioner (ACP) certification from PMI, and I’ve already updated my ACP course to reflect all of those changes. I wanted to take a moment to give you a behind-the-scenes look at these updates, show you what’s new, and highlight all the amazing additions that match the updated exam content outline. If you’re planning to sit for the ACP exam, these updates are crucial for your preparation.

New Eligibility Requirements for the ACP Exam

First things first, the eligibility requirements for the ACP exam have changed. To be eligible for the exam, you need:

  • A secondary diploma (high school or equivalent).
  • 28 contact hours of agile education. My course covers these 28 hours, ensuring you meet this requirement. You can still use 21 hours until March 31, 2025, but with my course, you’re already set with the full 28 hours.
  • Two years of agile experience, or a current PMP.

I’ve also added content to my course to specifically cover the 28 contact hours, including agile frameworks, methodologies, and practices. This ensures you’ll be fully prepared for the new requirements.

What’s New in the Course?

I’ve worked hard to update the course and ensure it aligns with the new exam content. Here’s a breakdown of the major updates:

General Introduction to Agile

We begin with a general introduction to agile – covering the basics of agile practices, frameworks, and methodologies. This section sets the foundation for the course, ensuring you understand agile in a project context.

Updated Exam Content Outline

Next, we dive into the updated ACP exam content outline. I’ll guide you through the key concepts and principles you need to focus on, making sure you’re aware of everything that’s relevant for the new exam format.

Real Project Matched to the ACP Exam

One of the most exciting additions to the course is a fully-realized project that matches the new ACP exam content outline. In this section, we go step-by-step through the process of delivering a web app for a fitness company. It’s not just theoretical – this project provides real, practical insights, and every stage is directly tied to the ACP exam’s learning objectives.

Comprehensive Agile Frameworks

I’ve also included an in-depth exploration of all the key agile frameworks, including:

  • Scrum
  • Extreme Programming (XP)
  • Kanban
  • Feature-Driven Development (FDD)
  • Crystal
  • SAFe (Scaled Agile Framework)
  • Large Scale Scrum (LeSS)
  • …and much much more.

These frameworks are crucial to understanding agile at a deeper level, and we dive deep into each one to ensure you’re well-versed in how they work.

Agile and Executive Coaching

Another standout feature of this updated course is the inclusion of agile and executive coaching. Having worked as an agile coach myself, I’ve seen firsthand how organizations often struggle with agile transformation. In this section, I provide valuable insights on coaching executives and addressing common challenges within agile projects. This coaching information is something you won’t find in many other courses, and it’s sure to take your knowledge to the next level.

Agile Transformations: Changing Organizational Culture

Beyond just implementing agile within projects, we also cover agile transformations – how to change an entire organization’s culture to become agile. This part of the course provides high-level strategies and steps to guide organizations through the agile transformation process, making sure they’re set up for success long-term.

Quick Review of Key Agile Concepts

To help you quickly refresh your knowledge, I’ve included around 100 key agile concepts that provide a concise review at the end of the course. This is a great resource for last-minute revision before the exam.

Practice Tests to Test Your Knowledge

One of the most valuable additions is the inclusion of two full practice tests, each with 120 multiple-choice, scenario-based questions. These practice tests are designed to mimic the real ACP exam, giving you the opportunity to test your knowledge and assess your readiness. You’ll find these tests cover all the topics you’ll encounter in the actual exam, so they’re a fantastic tool to help you prepare.

Final Thoughts: Become a True Agile Practitioner

By the end of the course, not only will you be ready to sit for the ACP exam, but you’ll also have practical, real-world agile knowledge that will make you a true agile practitioner. This course is designed to ensure that you not only earn the certification but also apply agile effectively in real projects.

Additionally, you’ll receive a certificate of completion once you’ve finished the course, providing proof of your newly acquired skills.

If you’re ready to dive into agile, learn practical techniques, and prepare for the ACP exam, I highly recommend checking out my updated course. You won’t be disappointed with the content I’ve added, and it will set you on the right path to becoming an Agile Certified Practitioner.

David McLachlan on LinkedIn

See more Agile Certified Practitioner articles: 

You can see what people are saying about David McLachlan here: REVIEWS

Navigate to Free Project Management and Leadership Articles through the links on the right (or at the bottom if on Mobile) 

PMI PMP 35 PDUs CourseThe Ultimate PMP Project Management Prep Course (35 PDUs)
Agile Certified Practitioner (PMI-ACP 21 PDUs)The Complete Agile Course: PMI-ACP (21 PDUs), Coaching, Jira and MORE! 
50 Project Management Templates Gantt Chart Risk Matrix and more Excel50+ Project Management Templates in Excel and PowerPoint (Gantt Chart, Risk Matrix and more!)
Project Management Plan TemplatesPre-made Project Management Plan Template: Save 100 HOURS!

 

The Agile Manifesto is Being Corrupted – By Us

A Simple Manifesto for Complicated Humans

If you’re working in or studying Project Management, becoming familiar with the Agile Manifesto is crucial. Although it is brief and straightforward, its principles have had a huge impact on project management techniques for more than 23 years now.

The manifesto emphasizes core values like individuals and interactions, working software, customer collaboration, and responding to change, which have proven to be effective when working through complex situations. The only trouble is – as human beings we somehow cannot wait to complicate it again.

We add processes, extra names, extra functions, extra job roles, heck we even add extra departments to handle all this extra stuff we’ve added. The core of the Agile Manifesto is being corrupted, because it is actually hard work keeping things simple.

But the simplicity in the Agile Manifesto highlights a key truth: simple approaches often yield the best results, fostering clarity and efficiency in software development and project management.

Just as simple, refactored code is easier to maintain and less prone to errors than complex code, simple designs are more user-friendly and effective than their intricate counterparts. Embracing the simplicity of the Agile Manifesto allows teams to focus on what truly matters, leading to better outcomes. And doing that often leads to greater success and effectiveness, helping you and your team win.

See more Leadership articles: 

You can see what people are saying about David McLachlan here: REVIEWS

Navigate to Free Project Management and Leadership Articles through the links on the right (or at the bottom if on Mobile) 

PMI PMP 35 PDUs CourseThe Ultimate PMP Project Management Prep Course (35 PDUs)
Agile Certified Practitioner (PMI-ACP 21 PDUs)The Complete Agile Course: PMI-ACP (21 PDUs), Coaching, Jira and MORE! 
50 Project Management Templates Gantt Chart Risk Matrix and more Excel50+ Project Management Templates in Excel and PowerPoint (Gantt Chart, Risk Matrix and more!)
Project Management Plan TemplatesPre-made Project Management Plan Template: Save 100 HOURS!

 

The Secret History of Agile: From Japan to America

Note: Click on the video above to watch.

hand drawn comic software and car manufacturer working togetherThe Secret History of Agile: Unveiling the Roots of a Revolutionary Methodology

The Agile methodology, a transformative approach in software development, is often mistakenly attributed solely to the Agile Manifesto of 2001. However, the roots of Agile stretch much deeper into history, with influences from manufacturing and even early industrial practices. Let’s check out the lesser-known origins of Agile, and see how it has really evolved from the 19th century to today.

The Waterfall Model: A Misunderstood Beginning

The story of Agile cannot be told without mentioning the Waterfall model, traditionally seen as the “enemy” of Agile. Interestingly, Winston Royce, who formalized the Waterfall model, came up with a more iterative and feedback-driven approach in his final notes. Royce emphasized the importance of integrating feedback from testing into design and requirements, advocating for an iterative process and customer involvement.

This philosophy, remarkably similar to Agile, shows that even the origins of the Waterfall model came from principles that Agile later embraced.

Early Industrial Influences: Toyota’s Innovations

Agile’s principles can be traced back to early industrial practices, particularly those pioneered by Toyota. In 1896, Sakichi Toyoda introduced the “Stop and Notify” concept, also known as Jidoka or autonomation. His invention of an automatic loom that halted production if a needle broke was revolutionary, combining human oversight with machine efficiency. This concept of built-in quality control is a cornerstone of Lean manufacturing and, subsequently, Agile.

Post-War Innovation: The Birth of Lean and Kanban

The real transformation began in 1948 when Toyota faced severe resource constraints post-World War II. This led to the creation of the Toyota Production System, the precursor to Lean manufacturing. Lean emphasizes waste reduction and Kaizen, or continuous improvement. From Lean, Kanban emerged, a method of visualizing the work to optimize flow. This later became integral to Agile software development.

The Agile Manifesto: A Culmination of Decades of Ideas

Agile as formally recognized today was crystallized in 2001 with the Agile Manifesto, but its foundations were laid much earlier. The Manifesto was influenced by various methodologies, including Lean, Kanban, Extreme Programming, Feature Driven Development and Scrum. These frameworks collectively contributed to Agile’s emphasis on flexibility, customer collaboration, and iterative development.

Scrum: A Revolutionary Approach

Scrum, often synonymous with Agile, has its roots in a 1986 white paper titled “The New New Product Development Game” by Japanese researchers Hirotaka Takeuchi and Ikujiro Nonaka. They proposed a holistic, team-based approach to product development, likening it to a rugby team working together to move the ball down the field. This approach emphasized overlapping development phases, self-organizing teams, and continuous learning—key principles that underpin Scrum and Agile.

The Six Secrets of The New New Product Development Game

Takeuchi and Nonaka identified six characteristics of successful product development teams, which resonate strongly with Agile principles:

  • Built-in Instability: Assigning broad goals to capable teams, granting them autonomy and flexibility to meet that goal.
  • Self-organizing Teams: Teams acting like startups, from ideation to implementation, fostering autonomy, self-transcendence, and cross-functional collaboration (the Product Owner idea in Scrum today).
  • Overlapping Development Phases: Continuous interaction between research and development and production to ensure constant progress and iteration.
  • Multi-learning: Encouraging team members to pursue ongoing learning, both within and outside their areas of expertise.
  • Subtle Control: Implementing visual management and maintaining open workspaces to facilitate communication and collaboration.
  • Organizational Transfer of Learning: Converting project activities into standard practices to spread knowledge throughout the organization.

As you can see there are many similarities between Scrum as we know it today, and The New New Product Development Game introduced in 1986, even if some of the names are different.

Conclusion: The Ever-Evolving Journey of Agile

The history of Agile is rich and multifaceted, drawing from various disciplines and evolving over decades. From Royce’s iterative vision for Waterfall to Toyota’s Lean principles and the collaborative ethos of Scrum, Agile embodies a continuous pursuit of improvement and adaptability. Understanding this deep and varied history not only enriches our appreciation of Agile but also underscores its enduring relevance in today’s fast-paced, ever-changing technological landscape.

For those eager to dive deeper into Agile’s principles and practices, comprehensive courses and coaching can offer valuable insights and practical skills. Embracing Agile is not just about adopting a methodology; it’s about joining a long-standing tradition of innovation and excellence in product development.

See more PMP Articles and Tips for Passing your Exam: 

You can see what people are saying about David McLachlan here: REVIEWS

Navigate to Free Project Management and Leadership Articles through the links on the right (or at the bottom if on Mobile) 

PMI PMP 35 PDUs CourseThe Ultimate PMP Project Management Prep Course (35 PDUs)
Agile Certified Practitioner (PMI-ACP 21 PDUs)The Complete Agile Course: PMI-ACP (21 PDUs), Coaching, Jira and MORE! 
50 Project Management Templates Gantt Chart Risk Matrix and more Excel50+ Project Management Templates in Excel and PowerPoint (Gantt Chart, Risk Matrix and more!)
Project Management Plan TemplatesPre-made Project Management Plan Template: Save 100 HOURS!

 

The Three Cs of User Story Creation

3 C’s of User Story Creation

The Three Cs for User Story Creation

The three Cs are a great way to remember to collaborate and create items to work on in an Agile team. They stand for the Card, the Conversation and the Confirmation.

The Card

This is the customer requirement, often with "Acceptance Criteria" for what needs to be done. It is written on a card as a User Story, and often shown on a Kanban Board.

The Conversation

A Conversation between: customers or users, developers and testers – our “triad” or “three amigos” – to work through the requirements, solution, and acceptance test criteria.

The Confirmation

Confirmation that the item meets the requirements. The Customer can sign off the requirements, the team can Showcase the increment at the Sprint Review, and the Scrum Master can ensure a Definition of Done is in place for the team.

A Definition of Done is the criteria we have to meet for the card to be seen as "Complete". It might include developing it, testing it, demonstrating it and signing off on it.

Learn Project Management and earn 35 PDUs, Learn Agile and earn 21 PDUs, save yourself 100s of hours with the Excel and PowerPoint templates below.

You can see what people are saying about David McLachlan here: REVIEWS

PMI PMP 35 PDUs CourseThe Ultimate PMP Project Management Prep Course (35 PDUs)
Agile Certified Practitioner (PMI-ACP 21 PDUs)The Complete Agile Course: PMI-ACP (21 PDUs), Coaching, Jira and MORE! 
50 Project Management Templates Gantt Chart Risk Matrix and more Excel50+ Project Management Templates in Excel and PowerPoint (Gantt Chart, Risk Matrix and more!)
Project Management Plan TemplatesPre-made Project Management PLAN Template: Save 100 HOURS!

 

Secret Game #1

Click Me!

 

INVEST for User Story Creation

INVEST for User Stories

A Great Way to Create Agile User Stories

INVEST is an acronym that helps us when creating user stories. In an Agile team, you’ll typically get together in a “Triad” or “The Three Amigos” of the Customer, Developer and Tester, but it can be anyone who needs to have an input.

INVEST stands for:

Independent, Negotiable, Valuable (or Vertical), Estimable, Small and Testable.

Independent

The User Story should be a usable piece that can operate on its own, independent to others, that we can demonstrate at the end of the Sprint.

Negotiable

The User Story should be able to be negotiated in our out of the sprint, or even out of the Product Backlog if it is no longer valuable. We should be able to negotiate the requirements against the solution.

Valuable

The item should have customer value, and be able to be demonstrated.

Estimable

The item’s effort should be able to be estimated by the team.

Small

It should be small enough to be completed in a Sprint (usually around 2 weeks)

Testable

It should be testable – often the team will write the tests (or acceptance criteria) first using “Test Driven Development”.

Learn Project Management and earn 35 PDUs, Learn Agile and earn 21 PDUs, save yourself 100s of hours with the Excel and PowerPoint templates below.

You can see what people are saying about David McLachlan here: REVIEWS

PMI PMP 35 PDUs CourseThe Ultimate PMP Project Management Prep Course (35 PDUs)
Agile Certified Practitioner (PMI-ACP 21 PDUs)The Complete Agile Course: PMI-ACP (21 PDUs), Coaching, Jira and MORE! 
50 Project Management Templates Gantt Chart Risk Matrix and more Excel50+ Project Management Templates in Excel and PowerPoint (Gantt Chart, Risk Matrix and more!)
Project Management Plan TemplatesPre-made Project Management PLAN Template: Save 100 HOURS!

 

Five Core Values of a Scrum Team

– See all the Agile Certified Practitioner Videos –

The Five Core Values of a Scrum Team

There are five Scrum values that all project team members, including the project manager (Scrum Master), strive to adhere to on a Scrum project.

Core Value 1 – Commitment

Each team member commits to the team, to each other, and to achieving the goal of each sprint.

Core Value 2 – Focus

The team focuses on the task at hand (avoiding the dangers of multi-tasking) and on the goals of the sprint.

Core Value 3 – Openness

The team is open and transparent – they share information freely and ask for help when they need it.

Core Value 4 – Respect

The team respects each other as capable, independent people.

Core Value 5 – Courage

The team has the courage to do the right thing, work through tough problems, ask for help if needed or say when they don’t know.

The Core Values of a Scrum Team

These core values of Scrum help hold a team together and form a contract (like a Team Charter) that creates a solid foundation as you work together towards your goals.

– David McLachlan

– See all the Agile Certified Practitioner Videos –

Seven Steps to Leading a Scrum Project

– See all the Agile Certified Practitioner Videos –

Seven Steps to Leading a Scrum Project

There are seven steps to leading a Scrum Project.

These are extremely useful to know if you are working on or within a project using Agile or Scrum.

Step 1

The product owner (representing the customer or end user) creates a prioritised list of everything the project might deliver.

This list is called the prioritised product backlog.

Step 2

The team and the Product Owner have a sprint planning meeting. The team decides how much work it can take on in the next sprint.

The team pulls requirements from the prioritized product backlog that it can achieve in the sprint. This work becomes the sprint backlog.

Step 3

The team decides who will do what and creates the task cards in the sprint backlog for the current sprint.

The team will meet each day for a 15-minute meeting, called the daily scrum (also called a stand-up), to share progress updates.

Step 4

The project manager, called the Scrum Master, helps keep the team working toward the sprint goal.

They remove blockers, bring people in to the whole team approach, and facilitate progress.

Step 5

A sprint review happens at the end of each sprint to demonstrate what the team has accomplished to the product owner.

Step 6

After the sprint review the team participates in a sprint retrospective to discuss what did or did not work in the last sprint.

This gives the Scrum Master and the team an opportunity to adjust the processes and work for the next sprint.

Step 7 

The whole process repeats itself by the project team selecting the next chunk of prioritized requirements from the backlog and getting to work in the next sprint.

Implementing Scrum

Implementing Scrum in an organization can be tricky, especially if no one in the organisation or team have done it before.

Show the value of Scrum through the results you get by using it, and more and more people will be interested in adopting the Scrum approach.

– David McLachlan

– See all the Agile Certified Practitioner Videos –