Scrum.org

FEBRUARY 25, 2020

I looked at how this can work out for your Daily Scrum , and now we've arrived at the last specific event of Scrum: the Sprint Review. A small reminder from the Scrum Guide: “A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. None of the team members knows what to say.

Development Team Review 135

Development Team Review SCRUM Closing Planning 135

Planio

SEPTEMBER 11, 2023

Planning: Define your project deliverables in more detail with a requirements workshop 4. Structure your project deliverables in this way, and they serve as good markers of your progress while providing clear checkpoints to pause, review, and learn. Initiation: Scope your high-level deliverables in your business case 2.

Software Review 88

Software Review Underperforming Technical Team Development Team Review Technical Review 88

Scrum.org

JANUARY 7, 2020

Do you frequently find yourself in Sprint Reviews that only consist of a PowerPoint presentation? For such an important part of the empirical process made possible by the Scrum Framework, the Sprint Review often receives the least attention in how it is facilitated. In this post, we share the design for a Sprint Review.

Software Review 111

Software Review Development Team Review SCRUM Closing 111

Scrum.org

MARCH 22, 2021

The purpose of qualitative metrics is to gain insight into how one or more of an organization’s Scrum Teams are progressing with agile. The interval to test via self-assessment is every 4–12 weeks, with teams of lesser fluency running their tests at the lower end of this range. Question 44: First Steps of a New Scrum Team.

SCRUM 227

SCRUM Underperforming Technical Team Development Team Review Technical Review 227

Scrum.org

DECEMBER 7, 2022

Consider a cadence that involves Planning, Reviewing, and Retrospecting with a clear distinction between the team working on the OKR and its stakeholders. . After identifying the few real OKRs, assess who’s needed to work towards each of them. The Scrum framework provides one example of how such a cadence could look.

Cadence 188

Cadence Development Team Review Initiating SCRUM 188

Scrum.org

MARCH 19, 2023

Here are some of the key differences between the two versions: Focus on the Scrum team : The Scrum Guide 2020 places more emphasis on the Scrum team, rather than just the Development Team. The Product Owner and Scrum Master are now considered equal members of the Scrum Team.

ChatGPT 152

ChatGPT SCRUM Technical Review 2020 152

Resource Guru

MARCH 20, 2023

Last week, Brett Harned shared his story about the importance of assessing project scope and involving the right people. I decided to facilitate a workshop where we would discuss the roles in Agile development and identify who was currently filling these roles. The day of the workshop arrived.

Development Team Review 52

Development Team Review Technical Review Software Review Governance 52

Rebel’s Guide to PM

MARCH 18, 2019

As project managers, it’s important that we know how to best support our development teams (and vice versa), especially in Agile environments. A lot of the points below relate to teams in Agile environments , but can apply to any type of project team. This is a guest post from Elisa Cepale. Elisa Cepale.

Technical Review 398

Technical Review Development Team Review Risk Management Agile 398

Scrum.org

JANUARY 10, 2021

I usually run at least the first refinement as a guided workshop. By running one before a Sprint Planning most teams will see the value of it by the end of the next Sprint. Start at the top and ask the Product Owner if this is the next most important thing?

2020 239

2020 Technical Review Development Team Review SCRUM 239

Scrum.org

DECEMBER 16, 2019

Professional Scrum Master (PSM-I) workshop has a module that talks about the Definition of DONE (DoD) and Technical Debt. Although this may vary significantly for every Scrum Team, members must have a shared understanding of what it means for work to be completed and to ensure transparency. Let us take a look at the DoD-.

Development Team Review 196

Development Team Review Software Review Technical Review SCRUM 196

Scrum.org

APRIL 11, 2019

I advise to start finding one person to be the single Product Owner for all teams. The other “fake PO’s” should be moved inside the development teams as subject matter experts so they can provide detailed requirements. The Product Owner should develop an inspiring vision and a plan to make it happen.

Underperforming Technical Team 143

Underperforming Technical Team SCRUM Development Team Review Software Review 143

Scrum.org

OCTOBER 12, 2020

As per Scrum Guide – The Sprint Goal is an objective that will be met within the sprint by implementing the Product Backlog , and it guides the Development Team on why it is building the Increment. The scrum team discusses what can be done based on the definition of done and crafts the Sprint Goal and forecast their work.

Planning 253

Planning Technical Review Development Team Review Software Review 253

Scrum.org

NOVEMBER 7, 2018

In real life, these Product Owners are typically accountable to the value delivered by these multiple teams and rely upon a lot of assistance from the Development Teams in order to deal with the challenge of scale. . Large Scale Scrum and Nexus prefer to have one Product Owner for the entire product with one Product Backlog.

SCRUM 137

SCRUM Development Team Review Technical Review Cadence 137

Planio

DECEMBER 18, 2023

Take the time to reflect on any things you’d like to keep doing, and things you’d like to improve on, by reviewing lessons learned from the previous year. Before you even think about your own strategy, take the time to review and understand your organization’s missions, goals, and values. Get honest feedback from executives.

Planning 88

Planning Development Team Review Risk Management Software Review 88

Scrum.org

NOVEMBER 12, 2018

This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised. The Scrum Team decides how and when refinement is done. The Development Team. Meetings can be included.

SCRUM 152

SCRUM Development Team Review Estimate Software Review 152

Leading Answers

JANUARY 16, 2021

Assessing the chances of loss or gain occur throughout all forms of business and relies on taking an economic view of decision making. Instead, I believe many projects leave a lot of development team sourced opportunities unactioned. How are our team risk management capabilities developing?

Risk 145

Risk Underperforming Technical Team 2006 2012 145

Project Pulse Journal

APRIL 8, 2024

Improved Risk Management This component empowers teams to anticipate and mitigate potential risks by selecting a development approach tailored to the project's unique nature. Incorporating advanced risk assessment models enables a deeper understanding and identification of possible pitfalls.

Underperforming Technical Team 52

Underperforming Technical Team Cadence Development Team Review Technical Review 52

Scrum.org

JUNE 22, 2019

So this can be a developer, analyst, tester, designer or architect etc. Sprint Review at Schiphol Airport with lot’s of stakeholders. Examples of a Developer Culture. Examples that I’ve experienced and consider part of a Developer Culture are…. Development Teams are considered the most important part of the organization.

Underperforming Technical Team 150

Underperforming Technical Team Technical Review Software Review Development Team Review 150

Scrum.org

FEBRUARY 4, 2020

“The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team.” Then move to cross-functional teams to improve the team’s ability to deliver. Otherwise, the team – and the Product Owner – need a workshop on writing user stories.).

Development Team Review 193

Development Team Review Underperforming Technical Team SCRUM Technical Review 193

Scrum.org

NOVEMBER 7, 2018

In real life, these Product Owners are typically accountable to the value delivered by these multiple teams and rely upon a lot of assistance from the Development Teams in order to deal with the challenge of scale. . Large Scale Scrum and Nexus prefer to have one Product Owner for the entire product with one Product Backlog.

SCRUM 112

SCRUM Development Team Review Technical Review Cadence 112

Scrum.org

JANUARY 9, 2023

Follow-up question : Why is it beneficial that the team adheres to the values and practices of Scrum? This can help improve the overall quality of the team's work and ensure that the team is meeting its goals. Question : Should a Scrum Master remove problems on behalf of the Scrum Team? In-person and remote attendees.).

ChatGPT 219

ChatGPT SCRUM Underperforming Technical Team Technical Review 219

Scrum.org

NOVEMBER 24, 2021

Which activities can be fulfilled by others in the team, and what is needed for that? One of the reviewers of this article, Maarten Dalmijn , noted that he missed “product discovery” as a core activity in the work by Bass (2018). Maarten, who is an experienced Product Owner, added that he spends a lot of time on this with his teams.

2014 214

2014 2008 Technical Review 2019 214

Scrum.org

DECEMBER 8, 2023

They can identify gaps, offer innovative solutions, and provide feedback the core development team might overlook. The stakeholder feedback loop In the Scrum approach, iterative development and feedback go hand in hand. Their insights, stemming from various backgrounds and expertise, play a key role in shaping the Product Goal.

Influencer 158

Influencer Development Team Review Agile SCRUM 158

Project Pulse Journal

APRIL 15, 2024

Limit Work in Progress (WIP) – By limiting WIP, Kanban encourages teams to complete current tasks before taking on new ones, thus reducing multitasking and focusing on quality and efficiency. Feedback Loops – Incorporate regular meetings to review and adapt your workflow based on feedback.

Software Review 52

Software Review Technical Review Agile SCRUM 52

Proofhub

NOVEMBER 22, 2023

Since the digital landscape is always evolving, you need to periodically review and refine your site’s design, ensuring it remains fresh, user-friendly, and in line with current trends. CTA- Easily communicate and collaborate with your team, clients, and stakeholders in real-time with ProofHub’s Chat.

Development Team Review 78

Development Team Review Technical Review Underperforming Technical Team Software Review 78

Scrum.org

MAY 5, 2020

Due to the COVID-19 crisis, chances are that everyone in your organization is working from home. This includes your Product Owner and Development Team. How does working remotely impact the collaboration with the Development Team? For example, the Daily Scrum is attended by the Development Team only.

SCRUM 175

SCRUM Development Team Review Technical Review Consulting 175

Scrum.org

SEPTEMBER 8, 2020

While everyone will appreciate the effort, participating in a 2-day workshop does not mean that they mastered navigating the waters of dual-track Scrum, for example. Instead, the management ought to provide the teams with goals and guidance on how to achieve these, along with funding sufficient to meet the objectives.

Software Review 194

Software Review Agile Underperforming Technical Team Development Team Review 194

Scrum.org

APRIL 1, 2022

Long has spoonfeeding solutions and off-the-shelf feature descriptions prevailed in many development teams. Although some issues might have been fixed, I rarely see the full potential of a Scrum Team being achieved. If you’re a leader in your organization, please look around you and assess the state of psychological safety.

Underperforming Technical Team 214

Underperforming Technical Team SCRUM Innovation Leadership 214

MPUG

AUGUST 14, 2023

Some companies have this well-designed, perhaps pairing product development competent talent with sales talent during the opportunity period. Doing so imparts the scope to the development team even while in the opportunity stage, but this comes at a cost. For example, what happens if the opportunity never becomes a project?

Underperforming Technical Team 52

Underperforming Technical Team Development Team Review Estimate Closing 52

Scrum.org

MAY 7, 2019

One of the responsibilities of a Scrum Master is to coach the Development Team in self-organization. Therefore, it’s up to the Development Team to determine the best way to accomplish its work and build ‘Done’ Increments. Sprint Review. Liberating Structures provide boundaries for self-organization. Presentation ?

SCRUM 182

SCRUM Development Team Review Leadership 2018 182

The IIL Blog

SEPTEMBER 6, 2023

The Benefits of Agile Project Management Agile project management often results in the early release of benefits due to its incremental nature. Flexibility is gained as development teams are empowered to adapt the solution as the project progresses. How to assess the success of an Agile project.

Agile 88

Agile Underperforming Technical Team Software Review Development Team Review 88

Scrum.org

FEBRUARY 4, 2020

The participants of this session are the full Scrum Team: Product Owner, Development Team and the Scrum Master. Scenario A: After the Sprint Review, the team members stay in the same room. Scenario B: After the Sprint Review, the team members leave the room to take a fifteen minute break outside.

Development Team Review 128

Development Team Review SCRUM Innovation Planning 128

Scrum.org

OCTOBER 28, 2022

Long has spoon-feeding solutions and off-the-shelf feature descriptions prevailed in many development teams. Although some issues might have been fixed, I rarely see the full potential of a Scrum Team being achieved. If you’re a leader in your organization, please look around you and assess the state of psychological safety.

Underperforming Technical Team 167

Underperforming Technical Team SCRUM Innovation Leadership 167

Planio

MARCH 27, 2023

Unfortunately, too many project managers and development teams are eager to build and skip the stakeholder analysis stage. Stakeholder analysis involves identifying the people associated with your project, grouping them, assessing their needs, and planning how to manage them. Lessons learned review. Org chart review.

Planning 78

Planning Development Team Review Influencer Initiating 78

Scrum.org

AUGUST 17, 2020

A Scrum Team’s communication with stakeholders should not be run through a gatekeeper (e.g. solely through the Product Owner) because this hurts transparency and negatively affects the team’s performance. There is greater respect among stakeholders for the product delivery teams. Question 03: Impediment Remover.

SCRUM 231

SCRUM Technical Review Software Review Agile 231

Scrum.org

JUNE 18, 2021

What team cognition looks like for Scrum teams, and what signs tell you whether it's there or not. What research in this area tells us about how you can design, support, and encourage teams to develop team cognition and become high-performing. Pictures of a session where we created a skill matrix with a team.

2010 184

2010 SCRUM 2006 Software Review 184

Scrum.org

OCTOBER 7, 2019

Goodhart’s law states that a metric ceases to be a useful metric once it becomes a target, for example, for a performance review, because participants figure out how to game the system. However, it turns into the opposite if unleashed upon a less experienced team for productivity reporting purposes by the management.

Agile 174

Agile Underperforming Technical Team Estimate SCRUM 174