Scrum.org

MAY 17, 2021

That means that they need to have some level of knowledge of both the relevant business domain to help the Product Owner, as well as enough technical knowledge to help the Scrum Team. Are technical skills required to be a Scrum Master? Applicable knowledge of the technologies used by the team] .

Technical Review 140

Technical Review SCRUM Development Team Review Certification 140

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. Sprint Review.

Agile 309

Agile Software Review Technical Review Development Team Review 309

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 224

SCRUM Underperforming Technical Team Development Team Review Technical Review 224

Scrum.org

FEBRUARY 25, 2024

Scrum Anti-Patterns GPT’s Answer Organizational issues often lead to Scrum anti-patterns that can hinder the effectiveness and efficiency of Scrum Teams. Lack of Stakeholder Engagement : Failure to involve key stakeholders in Scrum events, leading to misaligned expectations​​.

SCRUM 223

SCRUM ChatGPT Technical Review Development Team Review 223

Scrum.org

MARCH 2, 2020

The following list of Scrum stakeholder anti-patterns addresses Scrum events, system-related issues as well as issues of individual players. Scrum Stakeholder Anti-Patterns at Scrum Event Level. Any of the examples will impede the team’s productivity and might endanger the Sprint goal. The Sprint Review. The Sprint.

SCRUM 243

SCRUM Development Team Review Underperforming Technical Team Technical Review 243

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. Code Complete.

Development Team Review 190

Development Team Review Underperforming Technical Team Software Review Technical Review 190

Scrum.org

OCTOBER 12, 2020

On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. Keeping technical debt at bay. A good Scrum Team pays attention to the preservation of an application’s technical health to ensure the Scrum Team is ready to actually pursue an opportunity in the market.

SCRUM 234

SCRUM Underperforming Technical Team Technical Review Software Review 234

Scrum.org

JULY 7, 2024

Solitary Prioritization by the Product Owner Detail : In this approach, the Product Owner (PO) independently reviews and updates the Product Backlog. This method can be efficient for initial grooming but may miss out on valuable input from the development team and stakeholders. Pros : Efficient, aligns with product vision.

Technical Review 209

Technical Review Development Team Review 2024 Estimate 209

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 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 157

SCRUM Development Team Review Technical Review Cadence 157

Scrum.org

NOVEMBER 6, 2023

Scrum’s events, roles, and artifacts give you a framework for how to wrangle the humans — herd the cats, if you will — in order to deliver done, working software. Technical prowess on the instrument does not necessarily lead to musicality. Each Thing in Scrum Relates to Delivery Scrum is made up of roles, events, and artifacts.

SCRUM 214

SCRUM Software Review Development Team Review Technical Review 214

Scrum.org

MARCH 22, 2021

Join more than 100 peers from May 27-29, 2021 , for the Virtual Agile Camp Berlin 2021, a non-profit live virtual Barcamp using open space technology principles and practices. The team addressing unplanned priority bugs. Has the level of technical debt increased or decreased during the last Sprint?

SCRUM 235

SCRUM Underperforming Technical Team Development Team Review Technical Review 235

Scrum.org

NOVEMBER 9, 2020

The following Sprint Planning checklist includes tasks for everyone on the Scrum Team: Preparing the Sprint Planning: T-2 : Address the number of open tickets in the “code review” & “ready for acceptance columns.” Ask the team members to focus on moving tickets to “Done” before starting work on new tickets.

Planning 209

Planning Technical Review Software Review SCRUM 209

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

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. Remote Facilitation.

SCRUM 217

SCRUM Development Team Review Technical Review Consulting 217

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? Or is this terra incognita?

ChatGPT 227

ChatGPT SCRUM Underperforming Technical Team Technical Review 227

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

NOVEMBER 24, 2021

They interviewed 55 practitioners and observed hundreds of Scrum events to categorize the activities that Product Owners spend their time on. Intermediary : Acting as an interface between management and the team and the process of disseminating domain knowledge. Data from our Scrum Team Survey may shed a light on this.

2014 233

2014 2008 Technical Review 2019 233

Scrum.org

OCTOBER 30, 2020

You can use them during the start of a new Scrum Team, at a meetup with other Scrum Masters, or to improve the collaboration with other Scrum Teams. The most obvious applications for using these questions are the various Scrum events and activities. Sprint Review. The Sprint Review happens at the end of a Sprint.

Technical Review 235

Technical Review SCRUM Development Team Review Consulting 235

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 217

SCRUM Development Team Review 2012 Technical Review 217

Scrum.org

JULY 10, 2018

While working diligently behind feature flags, using elements of Scrum, it wasn’t clear to the stakeholders the value being delivered and how well the teams were progressing towards their end goal. Development teams are structured and empowered by the organisation to organise and manage their own work.

Technical Review 118

Technical Review Development Team Review 2017 Engineering 118

nTask

AUGUST 22, 2019

This framework contradicts the traditional Waterfall approach, which is based on extensive analysis, planning of requirements and documentation before starting the development phase. This method often results in low-quality products due to delays in milestones, financial issues and lack of prioritized characteristics for the products.

SCRUM 132

SCRUM Technical Review Development Team Review Software Review 132

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. Increased software quality can be demonstrated by measurably less technical debt, fewer bugs, and less time spent on maintenance.

SCRUM 234

SCRUM Technical Review Software Review Agile 234

Scrum.org

FEBRUARY 1, 2021

(All Scrum team members need to communicate with stakeholders and customers to avoid losing critical information in translation. That is a reason for having, for example, the Sprint Review with stakeholders and customers.) ????. The technologist : “Define a future-proof technology stack in accordance with the overall IT architecture.

Technical Review 209

Technical Review 2020 SCRUM Development Team Review 209

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 117

SCRUM Development Team Review Technical Review Cadence 117

Scrum.org

OCTOBER 19, 2020

Daily Scrums are an important part of Scrum, but not all Daily Scrums need to be formal — a Development Team should not have a Daily Scrum for the sake of having it; it serves a different purpose than ticking off a box on a checklist. A small, experienced, and co-located team may use a morning coffee break for their Daily Scrum.

SCRUM 193

SCRUM Underperforming Technical Team Software Review Development Team Review 193

Scrum.org

FEBRUARY 21, 2023

I am committed to staying up-to-date with the latest industry trends, technologies, and best practices to continuously improve product strategy and drive business outcomes. Finally, I value collaboration and teamwork and believe in creating a supportive environment where the development team can thrive and achieve their best work.

ChatGPT 172

ChatGPT Development Team Review Technical Review SCRUM 172

Alan Parker Blog

AUGUST 16, 2024

The technological infrastructure of an organisation plays a pivotal role in maintaining the security, integrity, and availability of information. Adhering to these technological controls can significantly reduce risk exposure and protect organisations' most valuable digital assets against internal and external threats.

Technical Review 52

Technical Review Controlling Software Review Development Team Review 52

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 194

Agile Underperforming Technical Team Estimate SCRUM 194

Leading Answers

JUNE 22, 2022

Authentic leadership is practiced on mundane things, yet when more significant events occur, the skills and trust of others can be used to overcome significant hurdles. We must also be able to make the team feel capable and develop team members to their fullest potential. Why pay twice for the same opinions?”.

Leadership 193

Leadership Underperforming Technical Team Development Team Review Lean 193

Scrum.org

MAY 7, 2019

Facilitator : Open Space Technology , Conversation Cafe , 25/10 Crowd Sourcing. 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.

SCRUM 195

SCRUM Development Team Review Leadership 2018 195

Scrum.org

MAY 6, 2019

The Sprint Goal is a phrase that can be used in many different ways: The Development team uses it at every Daily Scrum, to inspect the work done and adapt the work left. Is it defined in a way that provides guidance and flexibility to the Development Team? Is this Sprint Goal understandable and transparent to everyone?

Development Team Review 158

Development Team Review SCRUM Technical Review Defining 158

The IIL Blog

OCTOBER 17, 2023

Agile team A cross-functional group of individuals (e.g., Product Owner, Scrum Master, Development team members) who work collaboratively to deliver value in an Agile project. Backlog A list of tasks, features, or requirements to be addressed by an agile project manager or team and is often associated with Agile methodologies.

Development Team Review 148

Development Team Review Project Life Cycle Underperforming Technical Team Estimate 148

Scrum.org

JANUARY 14, 2021

Empiricism via working integrated increments every Sprint - System Demo & Nexus Sprint Review meeting a common Definition of “Done”. The Nexus Sprint Review and the System Demo are similar events happening on a similar cadence - every several weeks (Sprint/Iteration). Important Differences. Nexus - ART.

Cadence 107

Cadence Technical Review Development Team Review Lean 107

Project Bliss

MAY 24, 2017

A project executed with waterfall methodology follows sequential phases as the team moves through planning and execution before delivering the final product to the customer. The project manager works with the project team and customer to determine the project scope. Review and Adjust. Scrum Master. Product owner. Collaboration.

Agile 185

Agile Software Review Underperforming Technical Team Technical Review 185

Scrum.org

OCTOBER 2, 2018

In contexts of growing business and technical uncertainty, those with the fastest feedback loop win. These are nice levels of transparency that are much better than just reviewing documentation of course, but they leave a lot to be desired. So, why the need for Continuous Deployment? Scrum Theory helps us out here.

Cadence 140

Cadence Development Team Review Technical Review Software Review 140

Scrum.org

OCTOBER 2, 2018

In contexts of growing business and technical uncertainty, those with the fastest feedback loop win. These are nice levels of transparency that are much better than just reviewing documentation of course, but they leave a lot to be desired. So, why the need for Continuous Deployment? Scrum Theory helps us out here.

Cadence 139

Cadence Development Team Review Technical Review Software Review 139