ProjectManager.com

FEBRUARY 14, 2023

Of course, it’s also helpful to estimate when the project will be completed, as noted above. These tasks are your product backlog. The product backlog is managed and prioritized by the product owner during the product as the scrum team prepares for its sprints. They can manage their backlog and collaborate when planning sprints.

Agile 346

Agile Estimate SCRUM Software Review 346

Scrum.org

OCTOBER 9, 2023

The Problem Early plans were to release a “Minimum Viable Experience” before year end. By late Spring, the Product Director described two “problems” and asked for my help: Release dates for the first publicly available version were slipping. Scope was expanding. They could not deliver a ‘Done’ increment on their own.

Transportation 171

Transportation 2011 SCRUM Initiating 171

Scrum.org

SEPTEMBER 26, 2023

Part of the Scrum Master accountability is finding effective tools for Product Backlog management, which often means that the Scrum Master is accountable for setting up the Scrum Board. In-person teams may use a physical whiteboard with sticky notes that progress across the board from “To Do” to “Done”.

Underperforming Technical Team 194

Underperforming Technical Team SCRUM Agile Software 194

Rebel’s Guide to PM

MARCH 18, 2021

Note: This article was put together before the PMBOK® Guide – 7 th edition was published so the information in it is drawn from publicly available information about what is going to be in the book. Assumption log Risk register Backlog (see, agile project artifacts are relevant too) Stakeholder register. You can grab the set I use here.

Logistics 509

Logistics Artificial Inteligence PMI Performance Measurement 509

Scrum.org

JANUARY 9, 2024

The moment a Product Backlog Item meets the DOD, an Increment is born. If a Product Backlog item does not meet the DOD, it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product Backlog for future consideration. The DOD applies to the Increment, not directly to the PBIs.

Technical Review 177

Technical Review Underperforming Technical Team Software Review 2024 177

ProjectManager.com

FEBRUARY 28, 2023

A product requirements document (PRD) lists the features you’ll include in your product release. You’ll find everything you need for your product to reach a successful conclusion and it’ll guide the development team throughout the release process. It shares the product plan with the team by showing all phases on one page.

Software Review 289

Software Review Development Team Review Budget Agile 289

Scrum.org

JANUARY 22, 2024

Back in November 2023, OpenAI released GPTs, a hyper-customizable version of their GPT-4-based chatbot. Please note that you need to have access to OpenAI’s paid version of ChatGPT to use GPTs.) Please note: I ran the following sessions on Sunday, January 21, 2024, from 7:10 am CET to 7:45 am CET on the model GPT-4.

ChatGPT 154

ChatGPT SCRUM Artificial Inteligence Agile 154

Scrum.org

MARCH 11, 2023

The aim of a Sprint is to create a ‘Done’ potentially releasable increment. It supports empiricism by providing transparency via building a shared understanding of what elements are required during product development to convert a Product Backlog Item (PBI) into a usable, valuable, potentially releasable Increment.

SCRUM 175

SCRUM Technical Review Underperforming Technical Team Software Review 175

Scrum.org

MARCH 11, 2024

Besides working on accomplishing the Sprint Goal, a Scrum Team also allocates time to product discovery, aligning with stakeholders, and refining the Product Backlog. It is an expensive Sprint Backlog anti-pattern.) However, once it moves from one backlog to the other, the Developers become responsible.

Technical Review 165

Technical Review Underperforming Technical Team SCRUM Software Review 165

Scrum.org

APRIL 11, 2022

TL; DR: 27 Product Backlog and Refinement Anti-Patterns. But even after a successful product discovery phase, you may struggle to create the right thing in the right way if your Product Backlog is not up to the job—garbage in, garbage out. Zur deutschsprachigen Version des Artikels: 27 Product Backlog Anti-Patterns. ??

Technical Review 246

Technical Review SCRUM Lean Agile 246

Rebel’s Guide to PM

JULY 20, 2023

Note: you’ll use these artifacts for project management across all the three performance domains. That includes: Comms management plan Release plan Requirements management plan Scope management plan Iteration plan Test plan Quality plan Logistics plan. I can see that being particularly relevant for things like a release plan.

Logistics 258

Logistics Artificial Inteligence PMI Performance Measurement 258

Scrum.org

MARCH 23, 2023

The Product Owner is empowered with the decision-making authority on all aspects of the product, including the release schedule, budget, order of the backlog, architecture, and technology. For instance ordering the Product Backlog, or deployment choices.

ChatGPT 194

ChatGPT Technical Review SCRUM Budget 194

nTask

AUGUST 5, 2021

Agile release planning plays a similar role in Agile processes. It is a project management methodology that aims to help you with sprint planning, releasing iteration, scheduling regular standup meetings, and using feedback to create a more optimized end product. What Is Agile Release Planning?

Agile 148

Agile Planning Technical Review Defining 148

Scrum.org

AUGUST 22, 2022

The moment a Product Backlog item meets the Definition of Done, an Increment is born.” . If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product Backlog for future consideration.”. “If

Technical Review 170

Technical Review SCRUM 2022 2020 170

Scrum.org

MAY 2, 2022

The primary way to achieve this goal as a PO is to manage the Product Backlog effectively. According to the Scrum Guide, this activity comprises: Developing and explicitly communicating the Product Goal; Creating and clearly communicating Product Backlog items; Ordering Product Backlog items; and, . Source : Scrum Guide 2020.

Technical Review 247

Technical Review Underperforming Technical Team Software Review SCRUM 247

Scrum.org

JULY 4, 2022

Continuous Delivery is the practice of automating your release pipeline. From code commit to releasing. Or management doesn’t want to invest because it would take time away from delivering more features, forgetting that each manual release already costs the team valuable time. Which manual tasks does it involve?

SCRUM 190

SCRUM Estimate Risk Management Process 190

Scrum.org

JANUARY 26, 2023

Note: transparency is way more than bringing “visibility”. Let’s take the Product Backlog. Do you still have a separate “release plan”.? You may want to check if and how you can show this information in your Product Backlog. Evaluate with your team how you can bring this information available through the Product Backlog.

SCRUM 170

SCRUM Initiating Controlling Planning 170

Scrum.org

AUGUST 27, 2022

The main steps of the session include the topic, timings, materials needed, facilitator (if co-facilitating), and critical notes. Discussion may also focuses on providing updates on budget and release forecasts. Finalize Product Backlog order, updated Release Forecasts, and Product Roadmap. ? Target Audience.

SCRUM 201

SCRUM 2022 Budget Planning 201

Scrum.org

JULY 4, 2022

Start to build your Product Backlog. Your active product goal should be in your product backlog but note that not everything in your product backlog has to directly relate to your product goal. Up until releasing then everything is simply a hypothesis. Make use of your Developers. Metrics, metrics, metrics.

SCRUM 226

SCRUM 2020 Lean Defining 226

Scrum.org

JUNE 1, 2021

Please note that I will continue using ‘role’ on occasions throughout this document, although the Scrum Guide 2020 now speaks of ‘accountabilities.’). The Developers then pick— considering all circumstances, for example, available capacity—those Product Backlog items they deem necessary to achieve the Sprint Goal.

Technical Review 215

Technical Review Software Review Planning SCRUM 215

Scrum.org

DECEMBER 9, 2021

The sketch below nicely summarises the importance of a Definition of Done and why it needs to represent releasable. The first step is to get transparency of all the activities needed to create a releasable, or valuable & useful product increment to your customer. Create a sticky note or card for each activity. Sky's the Limit!

Underperforming Technical Team 241

Underperforming Technical Team SCRUM Agile Certification 241

Scrum.org

JANUARY 16, 2024

Looking back at those previous releases that we had, those deployments that we had to the markets, did they actually make a difference? Kanban vs Scrum: the approach to the backlog In Kanban, the backlog is optional. Unlike in Scrum, where there is a product backlog, which is mandatory, it is an artifact.

Underperforming Technical Team 162

Underperforming Technical Team Innovation SCRUM Executing 162

Scrum.org

MAY 18, 2021

As you read through this it's important to note that it is as much about behaviours as it is about accountabilities. Ensuring that the Product Backlog is transparent, visible and understood. Ordering Product Backlog items. Choosing what and when to release. What does this mean? section for communication.

Certification 212

Certification Influencer SCRUM Closing 212

Scrum.org

NOVEMBER 24, 2021

Or writing items for the Product Backlog? They should develop and communicate the Product Goal, manage items and their ordering on the Product Backlog, and ensure that the Product Backlog is understood by stakeholders and team members. Note that Bass calls this “Groom” in reference to “Product Backlog Grooming”.

2014 216

2014 2008 Technical Review 2019 216

Scrum.org

APRIL 30, 2021

ordering the work in the Product Backlog so that the goals of the Scrum Team and the organization are best achieved. adding new work to the Product Backlog that needs to be done to the product and remove redundant work. So, it's all about the future work expressed as Product Backlog items in the Product Backlog.

Technical Review 226

Technical Review Estimate SCRUM Risk Management 226

Scrum.org

FEBRUARY 22, 2022

Please note that only legal and culturally accepted practices qualify as a suitable outcome. . Vision, Product Discovery & Product Backlog Management. Add items to the Product Backlog at your will. Micromanage the Product Backlog and its refinement; for example, insist on being present but rarely commit to attendance.

SCRUM 200

SCRUM Budget Agile 2022 200

Scrum.org

FEBRUARY 28, 2022

The work on the Product Backlog tends to be chock full of assumptions until they are completed and put into the hands of users. The best way to prevent the risk of un-done work is to make sure that each Sprint results — at least once — in a Done Increment that can be potentially released. Who needs to be involved in this?

SCRUM 174

SCRUM Technical Review Software Review Risk Management 174

Scrum.org

NOVEMBER 25, 2022

Create a Product Backlog. As a side note, the other factors for building trust are credibility and reliability as explained in the Trusted Advisor. Ask the team members to go wild and write everything they can come up with and pretend like no one is reading the sticky notes or the comments. Create the Product Backlog.

SCRUM 192

SCRUM Closing Consulting Planning 192

Scrum.org

APRIL 9, 2023

A couple of years ago, I asked by an executive how he would know if the money they invested on setting up these agile release trains was working? They ensure transparency and traceability for each Feature and Backlog Item to the purpose and vision of the organisation. I have been working on agile projects for the past 10 years.

Agile 211

Agile Innovation Executing Sustainability 211

Scrum.org

FEBRUARY 14, 2022

Misconceptions about Refinement — the process of adding detail, order and size to individual Product Backlog items can be highly detrimental to a team's ability to deliver value to the business frequently. Misconception # 1: The Product Owner alone is accountable for Product Backlog refinement. . Not all technical debt is bad.

SCRUM 163

SCRUM Underperforming Technical Team Software Review Technical Review 163

Scrum.org

SEPTEMBER 19, 2020

The Sprint Review is Empiricism at work: inspect the Product Increment and adapt the Product Backlog. It is the best moment to create or reaffirm the shared understanding among all participants whether the Product Backlog is still reflecting the best use of the Scrum Team’s resources, thus maximizing the value delivered to customers.

Technical Review 193

Technical Review Software Review Development Team Review Cadence 193

MPUG

JUNE 23, 2020

Slice out a release strategy. Each step is written on a sticky note, index card, or electronic card horizontally (from left to right ). Release Planning with a Story Map. After you have placed the epics, stories, and features in the story map based on the team’s capacity to deliver, releases can be determined.

Agile 122

Agile PMI Closing Risk Management 122

Scrum.org

SEPTEMBER 13, 2021

Please note that this is a 'Derek Definition' and not an official Scrum definition. Creating forecasts for Release and Product delivery dates. A typical format for Sprint Planning might look like this: The Product Owner brings an ordered Product Backlog to Sprint Planning. A Scrum Team. Within a Sprint. Breaking it down.

SCRUM 189

SCRUM Estimate Performance Measurement Planning 189

Scrum.org

FEBRUARY 22, 2022

The Product Backlog is one of the three Scrum artifacts. Each item on the list is called a Product Backlog item (PBI), and each PBI contains a description, sizing, and order. A well-refined Product Backlog is essential for high-performing Scrum Teams. So, how far out should the Product Backlog go ? .

Lean 176

Lean SCRUM Technical Review Closing 176

Scrum.org

FEBRUARY 24, 2020

(As the Sprint Backlog is emergent and new work may be identified as necessary to achieve the Sprint Goal, this attitude might leave the Development Team in the dark, risking the accomplishment of the Sprint Goal.). PO clinging to tasks : The Product Owner cannot let go Product Backlog items once they become part of the Sprint Backlog.

Development Team Review 249

Development Team Review Software Review SCRUM Engineering 249

Scrum.org

OCTOBER 9, 2023

For example, employ stakeholder satisfaction surveys post-release to justify modifications in stakeholder engagement practices, ensuring that the developed product aligns well with stakeholder expectations and organizational objectives. Example: Including a governance entity in the release process.)

SCRUM 151

SCRUM Technical Review Software Review Underperforming Technical Team 151

Scrum.org

JULY 12, 2021

However, please note that: The answers reflect the personal experience of the authors and may not be valid for every organization: what works for organization A, is likely failing in organization B. Hence, it would be best to support the Product Owner and the Developers to maintain a permanently “actionable” Product Backlog.

SCRUM 225

SCRUM Sustainability Agile 2019 225