Scrum.org

MARCH 13, 2020

This concept of refining makes some sense, but to plot it in that original process then seems hard. In order to turn this into a feature, to start developing it, this idea needs sharpening. Product Backlog Refinement is all about a shared understanding between Product Owner and the Development team. Who has to be there?

Development Team Review 237

Development Team Review Innovation Planning Process 237

Scrum.org

NOVEMBER 12, 2019

TL; DR: 15 Sprint Review Anti-Patterns. Answering this question in a collaborative effort of the Scrum Team as well as internal (and external) stakeholders is the purpose of the Sprint Review. Given its importance, it is worthwhile to tackle the most common Sprint Review anti-patterns. Are we still on the right track?

Development Team Review 172

Development Team Review Underperforming Technical Team SCRUM 2017 172

ProjectManager.com

MARCH 25, 2022

Agile project management came about as development teams worked towards getting products to the market faster. The waterfall methodology, which identifies a problem and then plans a solution, forces teams to stick to the requirements and scope of work that was defined at the beginning of the project. Agile Core Values.

Agile 370

Agile Software Review Technical Review Development Team Review 370

Scrum.org

SEPTEMBER 10, 2020

As Scrum is framework, your teams may be doing additional things in the events - which is fine,as long as they're getting value from doing the actions. Optimise the value of the work the Development Team perform Talk with customers. Ensure the Development Team understands items in the Product Backlog to the level needed.

Development Team Review 169

Development Team Review 2017 SCRUM Estimate 169

ProjectManager.com

JUNE 27, 2019

Scrum ceremonies are meetings that are unique to scrum teams. Scrum ceremonies ensure that everyone (the scrum master, product owner and development team) is in-sync. A sprint employs four different scrum ceremonies to ensure proper execution: sprint planning, daily scrum, sprint review and sprint retrospective.

SCRUM 294

SCRUM Underperforming Technical Team Development Team Review 2011 294

Scrum.org

JANUARY 17, 2020

The use of the terms Showcase, Show & Tell or Sprint Review. So which event is best to use? There is nothing wrong with a Show & Tell, Showcase or Sprint Review when used correctly to achieve the desired outcome. However, usage does not make them equal to each other as events that are interchangeable and the same.

Technical Review 200

Technical Review Development Team Review SCRUM Consulting 200

ProjectManager.com

NOVEMBER 22, 2021

The name is apt, as the waterfall methodology is a process in which the phases of the project flow downward. When implementing the agile methodology , project planning and work management are adaptive, evolutionary in development, seeking early delivery and are always open to change if that leads to process improvement.

Technical Review 505

Technical Review Prince2 Lean Manufacturing 505

Epicflow Blog

JULY 5, 2024

Reporting and analytics A robust capacity planning tool should generate reports and dashboards with insights into resource availability and capacity, allocation, and utilization, which will help managers track resource performance and assess the efficiency of project work. Why do you need capacity planning software?

2024 101

2024 Planning Development Team Review Consulting 101

Scrum.org

SEPTEMBER 8, 2020

Using the budgeting process as a Stage-Gate® to exercise control through the back door : The budgeting process is hard to align with agile requirements like the longevity of teams. Hence, the actual process will have to change over time. Actively participating in Daily Scrums is reserved for Development Team members. (It

Software Review 242

Software Review Agile Underperforming Technical Team Development Team Review 242

Scrum.org

MARCH 2, 2020

Often, these organizations were once created to train farm boys into assembly-line workers within a standardized industrial process churning out standardized products in the name of output optimization. The following list of Scrum stakeholder anti-patterns addresses Scrum events, system-related issues as well as issues of individual players.

SCRUM 243

SCRUM Development Team Review Underperforming Technical Team Technical Review 243

Scrum.org

SEPTEMBER 19, 2020

It's a key inspect and adapt opportunity for the Development Team, encouraging them check their progress towards the Sprint Goal and adjust their plan accordingly. It's also supposed to be an event for the Development Team and run by the Development Team but as we know in "the real world" it's not always implemented that way!

SCRUM 226

SCRUM Underperforming Technical Team Development Team Review Technical Review 226

Scrum.org

JANUARY 3, 2020

Within the scrum process, there are eleven basic elements that make up the framework. 3 roles, 3 artifacts, and 5 events. Practitioners need to learn to apply and understand the principles behind these in order to obtain the full benefits of the scrum process. The scrum process is often termed as a rinse and repeat process.

Process 161

Process SCRUM Development Team Review Engineering 161

Scrum.org

JUNE 8, 2021

These are the Daily Scrum, Sprint Planning, Sprint Review and the Sprint Retrospective. People new to Scrum tend to worry that with so many scheduled conversations that they or Scrum Team will suffer death by meeting! If the Development Team can take care of the problem themselves, they usually will. Did I miss something?

SCRUM 231

SCRUM Development Team Review Leadership Agile 231

Scrum.org

FEBRUARY 24, 2019

"The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of "Done" product at the end of each Sprint." - The Scrum Guide. The Scrum Guide is markedly ambitious in the standard of professionalism it demands of a team. Review Ready.

Development Team Review 191

Development Team Review Underperforming Technical Team Software Review Technical Review 191

Scrum.org

SEPTEMBER 13, 2021

Scrum Anti-Patterns: From Product Backlog to Sprint Review. I added new questions on Scrum anti-patterns, from the Product Backlog to the Sprint Planning to the Sprint Review, to provide more insight into the Scrum value creation process and the organization’s return on investment. Question 45: Scrum Master Anti-Patterns.

SCRUM 233

SCRUM Underperforming Technical Team Development Team Review 2020 233

Scrum.org

NOVEMBER 6, 2023

If I’m working with a company on their agile transformation or their implementation of Scrum or doing a Scrum training for their team, they’re not wrong in thinking that Scrum is important. If your focus is on the process , you’ll get good at the process. Development Team. It’s that Scrum isn’t the point.

SCRUM 214

SCRUM Software Review Development Team Review Technical Review 214

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. For example, a poster about Sprint Goals, the Definition of Done, or the Scrum Events. Encourage the team to resolve the impediments together. Things to try….

SCRUM 220

SCRUM Development Team Review Technical Review Consulting 220

Scrum.org

FEBRUARY 15, 2020

In the case of product development, there are a number of variables like people, process, technology, cultures, geographies, tools, skills, relationships, etc. Depending on the number of variables and variability within those variables, it is essential for teams or leaders to adapt their environment and style of decision making.

SCRUM 223

SCRUM Development Team Review 2012 Technical Review 223

Scrum.org

JANUARY 10, 2021

Most Scrum Teams that I encounter don’t do refinement of their Product Backlog and try to work on things that they don’t understand correctly. However, if you get to the Sprint Planning event and your backlog is not ready, then you are doing it wrong. You can come up with your Refinement event(s), or refine ad-hoc.

2020 241

2020 Technical Review SCRUM Development Team Review 241

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 159

Software Review Development Team Review SCRUM Closing 159

Scrum.org

OCTOBER 12, 2020

On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. This first set of the Scrum Master theses addresses their role in the Scrum process: Scrum is not a methodology, but a framework. Generally, insisting that the team achieve specific KPI, e.

SCRUM 234

SCRUM Underperforming Technical Team Technical Review Software Review 234

Scrum.org

JULY 5, 2022

During the first year of the pandemic, Scrum adoption more than doubled for software development teams. According to the 15th Annual State of Agile Report, the use of agile approaches for software development grew from 37% in 2020 to 86% in 2021. The Developers create the Sprint Backlog during the Sprint Planning event.

Underperforming Technical Team 218

Underperforming Technical Team SCRUM Software Review Development Team Review 218

Scrum.org

MAY 4, 2020

We had a look at common remote agile anti-patterns; we analyzed remote Retrospectives, Sprint Plannings as well as remote Sprint Reviews based on Liberating Structures. This eighth article now looks into supporting a distributed Development Team organizing a remote Daily Scrum. Do you want to get this article in your inbox?

SCRUM 215

SCRUM Agile Technical Review Development Team Review 215

Scrum.org

MARCH 22, 2021

This attitude is precisely why the 47 Scrum Master Interview Guide exists: Prevent imposters from slipping through the hiring process and causing damage. The purpose of qualitative metrics is to gain insight into how one or more of an organization’s Scrum Teams are progressing with agile. Read more : Product Backlog Refinement.

SCRUM 235

SCRUM Underperforming Technical Team Development Team Review Technical Review 235

Scrum.org

SEPTEMBER 17, 2020

Every situation is different, but my approach is to focus on today and do the things that are right to deliver value with a mind to the future; this may be either in terms of the choices you make to do something differently because of the future impact, or explicitly not and making a note for review when you grow the use of agile. .

Agile 254

Agile Technical Review Development Team Review SCRUM 254

Scrum.org

JULY 21, 2020

That is why we pay the Development Team to accept the responsibility to deliver a ‘done’ Product Increment. Waiting for the end of a sprint and a sprint review means waiting to ship a done project.” Or the Development Team is continuously delivering Increments during the Sprint. The statement is plain wrong.

Software Review 224

Software Review Underperforming Technical Team SCRUM Engineering 224

Scrum.org

NOVEMBER 7, 2018

To use the leadership styles model we discuss in the Leading SAFe class - the starting point is more of an orchestrating and technical expert kind of leadership stance and the goal should be to evolve towards a more serving the team and the process style over time. But we can't ignore the differences in lingo.

SCRUM 172

SCRUM Development Team Review Technical Review Cadence 172

Alan Parker Blog

AUGUST 16, 2024

Protecting these devices is critical as they can store, process, and access sensitive information. A formal process should be in place for requesting, approving, and assigning privileged access, and all privileged activities should be logged and monitored.

Technical Review 52

Technical Review Controlling Software Review Development Team Review 52

Scrum.org

DECEMBER 25, 2018

Besides these rules, there are also certain guidelines which help the Scrum Teams to make the best possible use of Scrum framework to create maximum Business Impact. For ex: You cannot do Scrum without the 3 Roles - Product Owner, Development Team and Scrum Master. The impact of it would vary based on team context.

SCRUM 172

SCRUM Development Team Review Estimate Budget 172

Scrum.org

NOVEMBER 25, 2019

What event could better embody Scrum’s principle of empiricism than the Sprint Retrospective? The Scrum Master encourages the Scrum Team to improve, within the Scrum process framework, its development process and practices to make it more effective and enjoyable for the next Sprint.

Underperforming Technical Team 247

Underperforming Technical Team SCRUM Development Team Review Agile 247

Scrum.org

AUGUST 29, 2022

Rather, the manager’s role — among other things — is to set the guardrails within which teams can self-manage. The self-management parameters will depend on the organization and the team’s maturity, which is the responsibility of the manager to assess. Processes that used to happen sequentially may be completed simultaneously.

Leadership 229

Leadership Agile SCRUM Development Team Review 229

Scrum.org

DECEMBER 7, 2022

People can use other processes to manage their work toward the OKRs. . Teams/Groups share their intent with each other and with relevant leaders to help ensure alignment in an environment of empowerment/autonomy. . After identifying the few real OKRs, assess who’s needed to work towards each of them. Cross-functional Alignment

Cadence 218

Cadence Development Team Review SCRUM Initiating 218

Scrum.org

FEBRUARY 11, 2020

You could therefore see the Scrum Master as a teacher; A Scrum Master might be having some coaching conversations with the Product Owner, managers, customers, Development Teams and other people or stakeholders in the organization, in order to help them gain a better understanding of Scrum. This doesn't mean booking (conference) rooms.

SCRUM 232

SCRUM Prince2 Risk Management Agile 232

Scrum.org

JANUARY 21, 2020

If you are talking about Kanban as a strategy for optimizing the flow of value through a process that uses a visual, work-in-progress limited pull system , then The Kanban Guide for Scrum Teams has some clear advice on how we make this happen. Why bother using Kanban and Scrum together? Work Item Age.

SCRUM 239

SCRUM Development Team Review Estimate Defining 239

Project Bliss

SEPTEMBER 13, 2021

These 4 stages in the framework are still widely used for understanding group development. Team leaders can use this framework to help teams mature for better performance. And because Agile teams are self-guiding teams, this model can be helpful for them, too. How to Use this Model for your Teams.

Development Team Review 279

Development Team Review Construction Leadership Agile 279

Scrum.org

FEBRUARY 25, 2024

Providing the content was a simple process and only took a few minutes. I was surprised that ChatGPT did not require some processing time, as it claimed it would be immediately available. Group them into categories such as culture, process, or organizational structure.

SCRUM 226

SCRUM ChatGPT Technical Review Software Review 226

Scrum.org

OCTOBER 19, 2020

This attitude is precisely why the 47 Scrum Master Interview Guide exists: Prevent imposters from slipping through the hiring process and causing damage. A small, experienced, and co-located team may use a morning coffee break for their Daily Scrum. A team waiting to ask for help is a team delaying progress.

SCRUM 211

SCRUM Underperforming Technical Team Software Review Development Team Review 211