Scrum.org

NOVEMBER 12, 2018

The Sprint Goal is mentioned 27 times in the Scrum Guide , Product Backlog refinement is only mentioned in the following piece (about the Product Backlog): Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. During Product Backlog refinement, items are reviewed and revised.

SCRUM 160

SCRUM Development Team Review Estimate Software Review 160

Scrum.org

FEBRUARY 16, 2020

Over my 15 years of experience with Scrum, I’ve observed velocity-driven and capacity-driven sprint planning as our ways of working when we figure out the amount of work the development team can take during a sprint. The development team decided to set a WIP limit of 10 on its Ready column based on its throughput run chart.

Planning 166

Planning Development Team Review SCRUM Closing 166

Scrum.org

JULY 29, 2019

In this article I discuss the proper way to use velocity if you are using it, the misuses and pitfalls, why it may be time for you to move beyond it, and suggest some metrics dimensions you should explore and experiment with. Your understanding of the definition is important - read it carefully. And that's important!

Technical Review 153

Technical Review Underperforming Technical Team Development Team Review Software Review 153

Scrum.org

SEPTEMBER 1, 2018

The Scrum is the whole of the Development team, the Product Owner and the Scrum Master. The Scrum team has affinity with the family of roles, yet it is not a role in the Scrum framework. The Scrum Master is servant leader for the Scrum team. The Daily Scrum is a 15-minute time-boxed event for the Development team.

SCRUM 103

SCRUM Development Team Review Software Review Influencer 103

Agilemania

APRIL 9, 2021

Note: I have written this article assuming the reader has working experience in Agile and know the concept of Velocity. ” In my experience, “Velocity” is used to measure the Productivity of the Development Team. I haven’t come across any definition of Velocity where the word Productivity is used.

Software Review 98

Software Review Development Team Review Initiating Consulting 98

Herding Cats

AUGUST 27, 2017

There's a recent post titled Four Fallacious Reasons to Estimate. It lists the usual suspects for why those spending the money think they don't have to estimate how much they plan to spend when they'll be done producing the value they've been assigned to produce for that expenditure. Let's look at each one in more detail.

Estimate 46

Estimate Software Review Underperforming Technical Team Technical Review 46

Scrum.org

MARCH 11, 2020

TL; DR: Development Team Anti-Patterns. After covering the Scrum Master and the Product Owner, this article addresses Development Team anti-patterns, covering all Scrum Events as well as the Product Backlog artifact. Do you want to get this article in your inbox? The Role of the Development Team in Scrum.

Development Team Review 236

Development Team Review Underperforming Technical Team Software Review Technical Review 236

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. That's a very broad definition.

Risk Management 137

Risk Management Risk Technical Review Underperforming Technical Team 137

Wrike

SEPTEMBER 3, 2023

This article will provide you with an in-depth guide on how to prevent project scope creep, from understanding its definition to implementing strategies and tools to control it. Imagine a software development project where the project manager estimated that it would take three months to complete.

Development Team Review 36

Development Team Review Technical Review Underperforming Technical Team Software Review 36

Planio

DECEMBER 14, 2018

Sprints are the backbone of any good Agile development team. But maybe more than that, sprint planning aligns the development team with the product owner. Like any relationship, the one between you and your team requires communication and clarity. Pro Tip: Use “Story points” to properly estimate tasks.

Software Review 107

Software Review Planning Technical Review Development Team Review 107

Scrum.org

SEPTEMBER 8, 2019

This article is the story of such a discovery. I met with my colleague, Ryan Kent , to discover his experience with Buggy Definitions (his term) in his environment. Ryan is a Scrum Master currently working with Agile teams in a multi-national insurance enterprise. Ryan : The team settled on this definition.

Artificial Inteligence 141

Artificial Inteligence Influencer SCRUM Defining 141

MPUG

APRIL 2, 2024

” This definition emphasizes the temporary and unique nature of a project, with a predetermined start and end date, as well as its focus on creating a specific outcome. Project Cost Management : This knowledge area focuses on the processes and activities required to plan, estimate, budget, and control the costs of a project.

Certification 52

Certification PMI Logistics Construction 52

Herding Cats

MAY 15, 2019

This paradigm is at the core of any business process of developing software. Story points were invented to bridge the need to answer these questions between the business and development team using a method for writing software that would later be called agile. Here's one of many definitions . Quickly estimate issues.

Software Review 37

Software Review Agile Development Team Review Estimate 37

Binfire

AUGUST 27, 2017

Project Estimation. How do you come up with project estimation in Agile world? Project estimation is hard not only in Agile but traditional methods as well. Project estimation is hard not only in Agile but traditional methods as well. Estimation for short run projects is always more accurate than for long projects.

Agile 97

Agile Technical Review Software Review Development Team Review 97

Binfire

APRIL 7, 2017

Project Estimation. How do you come up with project estimation in Agile world? Project estimation is hard not only in Agile but traditional methods as well. Most rigorous planning and estimation in the traditional project management method don’t make for on time delivery in 90% of project cases.

Agile 100

Agile Technical Review Software Review Development Team Review 100

nTask

OCTOBER 8, 2019

If you are in such a position that you are responsible for setting the direction and scope of a team to work on a project, then you should be able to write an effective Project Charter and in this article, we’ll guide you on project charter examples. Team Management. Let us begin. What is a Project Charter? Objectives.

Initiating 92

Initiating Budget Risk Management Development Team Review 92

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. Q 27: The ‘Definition of Ready’.

ChatGPT 227

ChatGPT SCRUM Underperforming Technical Team Technical Review 227

Leading Agile

NOVEMBER 13, 2018

You can find definitions online as easily as I. A metaphor usually captures some salient aspect of a Thing, but never comprehensively or definitively defines or describes the Thing. “Velocity” in software development doesn’t mean velocity. Estimated hours completed? What Is a Metaphor Not? Story points?

Software Review 113

Software Review Underperforming Technical Team Software Developers Software Development 113

Scrum.org

FEBRUARY 21, 2023

Shall I notify you about articles like this one? Additionally, I have a strong background in product discovery, which involves identifying customer needs, validating product ideas, and conducting experiments to inform product development decisions. Join Stefan in one of his upcoming Professional Scrum training classes !

ChatGPT 166

ChatGPT Development Team Review Technical Review SCRUM 166

Scrum.org

NOVEMBER 2, 2018

When we started back in July 2017 it was a standard ‘task radiator’ borrowed straight from the boards at work: The columns on this were: Product Backlog, Sprint Backlog, In Progress, Needs Review (I think that was the first to go!), They’re less a way of estimating a task and more a way of keeping score. Done, and Established Systems.

SCRUM 132

SCRUM 2018 Underperforming Technical Team Software Review 132

Teamweek

MARCH 25, 2024

Freelance developers and development teams often find it difficult to track their time efficiently and bill clients accurately. Time tracking software for developers can help overcome these challenges with automatic trackers, billing, and reporting features. What is the best time tracking software for developers?

2024 59

2024 Underperforming Technical Team Software Review Software 59

MPUG

AUGUST 14, 2023

This article delves into the potential challenges of transitioning from an opportunity to a project. Customer demands and aspirations drive sales teams, while project managers are responsible for delivering the project within defined constraints. When is it a Project? Not always, though.

Underperforming Technical Team 52

Underperforming Technical Team Development Team Review Estimate Closing 52

Scrum.org

FEBRUARY 4, 2020

Do you want to get this article in your inbox? The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team.” Everything is estimated: All user stories of the Product Backlog are detailed and estimated. You can sign up here and join 25k other subscribers.

Development Team Review 206

Development Team Review Underperforming Technical Team SCRUM Technical Review 206

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. It is, in essence, the plan for what the Scrum Team will do next.

Underperforming Technical Team 206

Underperforming Technical Team SCRUM Software Review Development Team Review 206

Scrum.org

JUNE 23, 2019

The following article points at 28 Product Backlog anti-patterns — including the Product Backlog refinement process — that limit your Scrum Team’s success. This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items.

Development Team Review 176

Development Team Review Technical Review SCRUM Estimate 176

Leading Agile

AUGUST 19, 2020

We’re starting to see HBR articles written more than one. How do we get a team to be able to make and meet commitments, right? So, the teams make and meet commitments by having a stack rank list of user stories, right? We typically want to have those stories estimated, right? They understand the acceptance criteria.

Agile 100

Agile SCRUM Governance Government 100

Scrum.org

JUNE 23, 2019

The following article points at ideas on how to improve your product backlog management techniques — including the Product Backlog refinement process. . This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items.

Development Team Review 171

Development Team Review Technical Review SCRUM Estimate 171

NimbleWork

APRIL 11, 2024

In this article, we delve into the significance of the WBS, its role in detailed project planning, and its application in different project management contexts. Although there isn’t a single definitive origin, the concept evolved over time as project management practices advanced.

Software Review 52

Software Review Development Team Review Risk Management Defining 52

MPUG

JUNE 23, 2023

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. In this article, we’ll provide an overview of Scrum fundamentals and the Scrum framework, including its roles and artifacts.

SCRUM 59

SCRUM Agile Development Team Review Technical Review 59

Scrum.org

SEPTEMBER 27, 2021

This latest update to the interview guide addresses Product Owner anti-patterns from Product Backlog management and refinement to the Sprint Review. Shall I notify you about articles like this one? Everything is estimated: All items of the Product Backlog are detailed and estimated. Sprint Review Anti-Patterns.

Underperforming Technical Team 199

Underperforming Technical Team SCRUM Technical Review Development Team Review 199

nTask

FEBRUARY 17, 2022

They are the absolute favorites of the agile project development teams and the DevOps teams that have to work on extensive projects with numerous elements attached to them. Time : One amazing thing about development teams is that most of them rely on estimation frameworks and not a fixed period of time.

2022 78

2022 Agile Development Team Review Estimate 78

Binfire

FEBRUARY 26, 2018

Harvard business review has written an interesting article titled why even good projects fail anyway. 3-Improper or insufficient scope definition. If the scope defined properly, it will be much easier to accurately plan and estimate the project duration. 6-Inexperienced development team.

Underperforming Technical Team 101

Underperforming Technical Team Technical Review Software Review Estimate 101

Herding Cats

NOVEMBER 29, 2017

The IMP should provide sufficient definition to track the step-by-step completion of the required Accomplishments for each event and to demonstrate satisfaction of the completion Criteria for each Accomplishment. Most IMPs in development programs include Events for major design reviews such as PDR or CDR.

Planning 42

Planning Software Review Governance Government 42

Herding Cats

JANUARY 23, 2019

Yet another class #NoEstimates lack of understanding of estimating, reference class forecasting, reference class databases, parametric estimating, estimating tools, and other well established estimating processes in the agile software development world. Subscribe to one of several reference class estimating sites.

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

Herding Cats

AUGUST 22, 2018

These are classic examples from an author who is either unskilled, untrained, and inexperienced in estimating software development. Or who willfully ignores the knowledge and resources readily available in textbooks, papers, tools, and training for how to create credible estimates for software systems. By simply NOT Estimating?

Estimate 35

Estimate Underperforming Technical Team Technical Review Software Review 35

Herding Cats

FEBRUARY 9, 2019

40 - Estimation is a Problematic Practice of Companies Doing Dangerous Things. A #Noestimates advocate makes the claim that having a ±10% accuracy for estimates of cost and duration is a dangerous thing. We develop these reference classes using Agile Function Points. Use these to develop a Systems Model of the products .

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

MPUG

JUNE 28, 2021

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. And fourthly, inaccurate cost estimates. I think a lot of this really is talking about even the definition of requirements, serves as a foundation, the basis of design.

Underperforming Technical Team 52

Underperforming Technical Team Technical Review Defining Project Life Cycle 52