Scrum.org

SEPTEMBER 23, 2019

The first article of this series will address the Scrum Master engagement with the Development Team. Scrum Master Engagement with the Development Team. Following this layout, there are three main scenarios for the Scrum Master’s support of the team: The Co-located, Stable Scrum Team Scenario.

Development Team Review 166

Development Team Review SCRUM Software Review Technical Review 166

nTask

OCTOBER 21, 2021

So, if you are in the market for information about the best tool for the job, then you came to the right place, because, in this article, we are going to talk about the best Linux project management software that you can use right now in 2021. 6 Best Linux Project Management Applications to Use Right Now in 2021. Table of Contents.

Technical Review 179

Technical Review 2021 Software Review Software 179

Scrum.org

FEBRUARY 25, 2024

Dive into how leveraging custom GPTs might offer a novel path through Scrum’s common hurdles, focusing on creating actual customer value in the face of organizational and team-level challenges. ? Shall I notify you about articles like this one? Join Stefan in one of his upcoming Professional Scrum training classes !

SCRUM 226

SCRUM ChatGPT Technical Review Development Team Review 226

Scrum.org

SEPTEMBER 14, 2020

Do you want to get this article in your inbox? An excellent suggestion on the part of your candidate would be for the Scrum Team to participate in gathering qualitative signals by taking part in user interviews. Please note: Normally, the Product Owner would provide this information during Sprint Reviews or the refinement process.

SCRUM 240

SCRUM Planning Development Team Review Technical Review 240

Rebel’s Guide to PM

AUGUST 7, 2023

You could also interview experts, review lessons learned or innovative solutions from previous projects, research what the rest of your industry is doing or consult customers on what they’d like to see. Choose the creative approach that gets you a range of options to review. There are no silly ideas at this point!

Technical Review 332

Technical Review Consulting Monitoring Development Team Review 332

Scrum.org

MARCH 18, 2020

Such a study is holistic; it involves looking at the organizational design, technical capabilities, culture and knowledge, and type of control and metrics used to define success. Some of these have to do with ‘the system,’ the whole of hierarchy, setups, technology, and so on that make up an organization.

Technical Review 191

Technical Review Underperforming Technical Team Software Review Development Team Review 191

Scrum.org

NOVEMBER 9, 2020

Do you want to get articles like this one from the Scrum Master Survival Guide in your inbox? 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.”

Planning 225

Planning Technical Review Software Review SCRUM 225

Scrum.org

APRIL 28, 2019

In a recent class, while trying to discover new metaphors to convey the true nature of Scrum, it came to my mind the term contextless (that sounds close to the "contactless" credit cards) to describe the mechanical, stringent and simple use of Scrum without considering the needs of the team or organization context.

Technical Review 167

Technical Review SCRUM Software Review Defining 167

Scrum.org

MARCH 22, 2021

Shall I notify you about articles like this one? 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. Are you happy working with your teammates?

SCRUM 235

SCRUM Underperforming Technical Team Development Team Review Technical Review 235

Scrum.org

MARCH 2, 2020

Do you want to get this article in your inbox? Any of the examples will impede the team’s productivity and might endanger the Sprint goal. The Scrum Master must prevent them from manifesting themselves: The Scrum Master has a laissez-faire policy as far as access to the Development team is concerned. The Sprint Review.

SCRUM 243

SCRUM Development Team Review Underperforming Technical Team Technical Review 243

Scrum.org

JANUARY 11, 2023

The product owner must have knowledge about the customer needs as well as technical expertise to ensure that the right decisions are made regarding feature selection. In this article we will explore what a day in the life of a Product Owner looks like. A Day in the Life of a Product Owner.

Technical Review 209

Technical Review Software Review Agile SCRUM 209

Scrum.org

OCTOBER 12, 2020

On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. Do you want to get this article in your inbox? Keeping technical debt at bay. Read more: Technical Debt & Scrum: Who Is Responsible ?). No one can force work upon the Development Team.

SCRUM 234

SCRUM Underperforming Technical Team Technical Review Software Review 234

Scrum.org

JANUARY 9, 2023

Shall I notify you about articles like this one? 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. Are we facing any dependencies on other teams?

ChatGPT 227

ChatGPT SCRUM Underperforming Technical Team Technical Review 227

Scrum.org

NOVEMBER 24, 2021

Intermediary : Acting as an interface between management and the team and the process of disseminating domain knowledge. This includes training, technical support, and preparation for new releases. Which activities can be fulfilled by others in the team, and what is needed for that? Insight #3: Product Discovery Is Missing?

2014 233

2014 2008 Technical Review 2019 233

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. This article is a small attempt to have better clarity on these topics. This is the definition of ‘Done’ for the Scrum Team and it is used to assess when work is complete on the product Increment.

Development Team Review 203

Development Team Review Software Review Technical Review SCRUM 203

Planio

FEBRUARY 17, 2025

Breaking it down: The 6 phases (and 6 gates) of the Stage Gate process Stage 0: Idea discovery Stage 1: Scoping Stage 2: Design Stage 3: Develop Stage 4: Validate and scale Stage 5: Launch Best practices for mastering the Stage Gate process Final thought: Is the Stage Gate process right for you? Reduces risks.

Software Review 88

Software Review Process Development Team Review Technical Review 88

Scrum.org

SEPTEMBER 13, 2021

Shall I notify you about articles like this one? 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.

SCRUM 233

SCRUM Underperforming Technical Team Development Team Review 2020 233

Moira Alexander

JANUARY 12, 2017

Sustainable development is accomplished through agile processes whereby development teams and stakeholders are able to maintain a constant and ongoing pace. Agility is enhanced through a continuous focus on technical excellence and proper design. To read this article in full or to leave a comment, please click here

Software Review 100

Software Review Technical Review Development Team Review Agile 100

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. The article contains many experiments, practices, and strategies you can try. It became a comprehensive article. What does remote facilitation look like?

SCRUM 220

SCRUM Development Team Review Technical Review Consulting 220

Digite

MARCH 12, 2018

That is, does the question below, which I answered on a technical forum recently, describe a situation you might be facing or may have faced in the past? Alternatively to the previous: I believe The IT Skeptic had an article about having two boards – one focused on the stakeholder epics, the other on the actual short-term tasks.

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

Scrum.org

JUNE 22, 2019

In this blog post, I’ll share examples of how I experienced a Developer Culture. Now, what I don’t want to do is write a vague article about culture full of fluffiness that might sound interesting but doesn’t provide any clarity. I’m simply going to share my perspective as a Scrum Master working closely with developers.

Underperforming Technical Team 184

Underperforming Technical Team Technical Review Software Review Development Team Review 184

Scrum.org

AUGUST 17, 2020

Do you want to get this article in your inbox? This article will cover the largest category of them — the role of the Scrum Master: The Background on the Role of the Scrum Master. A Scrum Team’s communication with stakeholders should not be run through a gatekeeper (e.g. Introduction. Scrum is not a methodology, but a framework.

SCRUM 234

SCRUM Technical Review Software Review Agile 234

Project Bliss

JANUARY 30, 2022

This article was originally published on September 30, 2016, and has been updated. Customer Communication – rather than the development team talking directly with the customer, the PM manages these communications. From the team level to the boardroom, where they’re looking at results and the bottom line.

Software Review 296

Software Review Technical Review Risk Management Budget 296

Scrum.org

FEBRUARY 1, 2021

Shall I notify you about articles like this one? 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.) ????. Source: Scrum Guide 2020, see above.) ????.

Technical Review 209

Technical Review 2020 SCRUM Development Team Review 209

Scrum.org

JULY 29, 2019

Doesn't product quality interest the developers, as well as code health and the amount of technical debt hiding beneath the surface? Team health? Flow of work, from the time the team starts working on a Product Backlog item until your customer is using it? What about business value metrics, I ask? And that's important!

Technical Review 181

Technical Review Underperforming Technical Team Development Team Review Software Review 181

The IIL Blog

JULY 31, 2024

Align with the Business Need A Guide to the Project Management Body of Knowledge ( PMBOK ), the bible for project managers, states that “projects are initiated due to internal business needs or external influences”. But that is not always the case, especially in technology. I’ll provide more information on them later in this article.

Technical Review 88

Technical Review Development Team Review 2013 Underperforming Technical Team 88

Scrum.org

FEBRUARY 21, 2023

Shall I notify you about articles like this one? 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. You can sign up here for the ‘Food for Agile Thought’ newsletter and join 36,000-plus other subscribers. ?

ChatGPT 172

ChatGPT Development Team Review Technical Review SCRUM 172

Scrum.org

MARCH 31, 2020

Many people around the globe are working from home right now, due to the Covid-19 pandemic. Despite the rapidness of the change, moving to remote worked surprisingly well for many teams, because they were used to some degree of remote work before. Personal assessment of risk is hampered by lack of information.

Underperforming Technical Team 206

Underperforming Technical Team 2020 2016 Technical Review 206

Scrum.org

AUGUST 6, 2020

The focus of this article is on one of the most important things giving lifeblood to the Product Backlog and promoting its characteristic of long-living artifact, the Innovation. technical debt : the technical debt we're accumulating (and that we need to reduce through activities like bug-fixing, or refactoring). . So what.

Innovation 194

Innovation SCRUM Technical Review Software Review 194

Scrum.org

DECEMBER 16, 2024

While Scrum excels in simplicity and flexibility, applying it out of the box often falls short in corporate contexts due to limitations in product discovery, scaling, and portfolio management. Shall I notify you about articles like this one? Can you rely on pure Scrum to transform your organization and deliver value? Not always.

SCRUM 183

SCRUM Technical Review Software Review Innovation 183

Scrum.org

JULY 10, 2018

Often I hear people say that Scrum does not take care of risk: there is no risk log, risk is not on the agenda of the Sprint Review or Retrospective as a standard agenda-item. The Development Teams need to be accountable for the quality of the product and how it's made. Technical risk - can it be made/build?

Risk Management 149

Risk Management Risk Technical Review Underperforming Technical Team 149

Project Bliss

MAY 10, 2017

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Working software is the primary measure of progress.

Software Developers 191

Software Developers Software Development Software Review Agile 191

Scrum.org

DECEMBER 9, 2018

This ‘seperate team’ pattern results in the ‘delivery sub-team’ being reduced to axe-grinding, code-wielding backlog lumberjacks (programmers & testers), do we want this? Research outside of the Scrum Team. A common scenario is where UX research is done outside of the Scrum team, or at least outside of the Development team.

SCRUM 173

SCRUM Agile Development Team Review Software Review 173

Scrum.org

OCTOBER 19, 2020

Do you want to get this article in your inbox? 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. Scrum Teams are no exception.

SCRUM 211

SCRUM Underperforming Technical Team Software Review Development Team Review 211

MPUG

FEBRUARY 5, 2025

One might conclude that agile approaches to project management, such as Scrum, mean there is no need for gate reviews. We say the same thing if one adopts gate reviews for every product development project. Let’s explore a typical product development project’s phases, goals, and metrics reviewed at each gate.

Development Team Review 88

Development Team Review Technical Review Manufacturing 2008 88

Scrum.org

DECEMBER 4, 2022

Shall I notify you about articles like this one? In business, it can help organizations respond to market trends, changing customer needs, and new technologies. For example, if a company is agile, it can quickly adapt to changes in market trends, changing customer needs, and new technologies.

ChatGPT 213

ChatGPT Generative AI SCRUM Agile 213

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