Scrum.org

MAY 13, 2024

Key Benefits of Verification: Early Defect Detection : Verification identifies potential issues early in the development process, reducing the likelihood of severe complications later on. Used Agile Practices : many Acceptance Criteria, Behavior Driven Development, Sprint Review, Definition of Done How do Verification and Validation Differ?

Technical Review 101

Technical Review Software Review Development Team Review Software Engineering 101

Agilemania

MARCH 14, 2023

The Definition of Done is the most crucial aspect for the team to be able to build shippable increments of any product. A team’s definition of done helps them continuously add value to the product. One way to think about the definition of done, is as a checklist that helps us guarantee the quality of the product.

Underperforming Technical Team 52

Underperforming Technical Team Technical Review Development Team Review Lean 52

Scrum.org

JANUARY 9, 2023

Does your team feel like too many defects are reaching production, but they aren’t sure what to do? I have worked with multiple teams who have encountered similar issues in the past. If this situation sounds familiar, this blog shows how to self-manage this problem. Let's investigate. Product Owner must approve PBI.

Software Review 184

Software Review Development Team Review SCRUM Initiating 184

Scrum.org

OCTOBER 12, 2020

I got the idea of writing this blog while hosting a webinar on the same topics when multiple people told us to document our discussion. Originally I posted this blog on Agilemania , and you can check our upcoming webinars there. The team picks up work for more than one product as they are supporting multiple products.

Planning 253

Planning Technical Review Development Team Review Software Review 253

LiquidPlanner

SEPTEMBER 6, 2018

In certain cases, it’s possible to cling to legacy or home-rolled project management practices even when development teams have moved into some form of Agile development. I’m ecstatic about how our development teams are delivering to our customers. Agile isn’t just for development and technical teams anymore.

Agile 755

Agile Executing Development Team Review Technical Review 755

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

Agilemania

MARCH 3, 2022

Development Team: The Scrum Development team is a cross-functional team so that they have the technical expertise to deliver the final product. The Development Team includes professionals like software developers, architects, programmers, analysts, system admins, QA experts, testers, UI designers, etc.

Certification 52

Certification Lean Development Team Review Engineering 52

Scrum.org

NOVEMBER 15, 2022

Now coming to the 3rd expectation which is the ‘HOW’ of sprint planning, the Developers and only developers are expected to plan the work necessary to create an increment that meets the definition of Done. What does that mean and how much to do, is what I plan to discuss in this blog. Code Review. Peer Review.

Planning 120

Planning Software Review Development Team Review 2017 120

Wrike

JULY 29, 2023

Analyze Current State: Assess current processes and performance to gain a thorough understanding of strengths, weaknesses, and inefficiencies. This allows organizations to assess the impact of the proposed changes and make any necessary modifications. This made the development team more efficient and motivated at work.

Development Team Review 36

Development Team Review Underperforming Technical Team Manufacturing Healthcare 36

Digite

MAY 15, 2018

In the most recent post in Steve Porter’s series, Yuval Yuret presents Scrum in a manner that is intended to educate Kanban teams. First off, I have to say that I’m not 100% certain how I feel about Yuval’s blog post. What will I do today to help the Development Team meet the Sprint Goal? Disclaimer.

Development Team Review 93

Development Team Review Software Review Underperforming Technical Team SCRUM 93

Scrum.org

SEPTEMBER 4, 2019

In today's blog, I want to talk about the evolution process of the Scrum team's Definition of Done and explain a simple technique that I found very useful in helping a Scrum team managing their Definition of Done. Definition of Done. If this is the case, continue to read this blog and start creating one ;).

Influencer 95

Influencer SCRUM Development Team Review 2017 95

Wrike

JUNE 23, 2023

Once you have a proof of concept in place, you can enter the development phase and effectively monitor progress with a project management solution such as Wrike. Try Wrike for free Proof of concept definition What is a proof of concept? Its application extends beyond physical products and into the development of technology or software.

Technical Review 36

Technical Review Artificial Inteligence Manufacturing Software Developers 36

Resource Guru

MARCH 20, 2023

Last week, Brett Harned shared his story about the importance of assessing project scope and involving the right people. The dev team appreciated the workshop because they felt seen and valued. But now, the whole team had the opportunity to grow—together. The day of the workshop arrived. Connect with Ordonna on LinkedIn.

Development Team Review 52

Development Team Review Technical Review Software Review Governance 52

Scrum.org

NOVEMBER 18, 2020

For a more detailed about the changes and how they can lead to some interesting discussions read my blog on the content changes. . What does this mean to the Assessments? Today there are no changes to the assessments. We plan that on January the 10th, we will update assessments to be based on the 2020 version of the Scrum Guide.

SCRUM 131

SCRUM 2017 Development Team Review 2021 131

Scrum.org

AUGUST 18, 2020

For the purpose of clarity my definition of Stakeholders is – Anyone and everyone directly and indirectly involved and/or impacted by the Product being developed except the Scrum Team; Users, Customers, Management, Leadership. . . . Stakeholders respect the autonomy and self-organization of the Development Team.

SCRUM 158

SCRUM Development Team Review Leadership Agile 158

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. . See a recent blog post I wrote about this). SAFe has a cadence at the Team and Program levels.

SCRUM 137

SCRUM Development Team Review Technical Review Cadence 137

Scrum.org

NOVEMBER 28, 2020

In this blog post, I will share what you need to know about the 2020 Scrum Guide. How a Scrum Team uses a Product Goal in practice is up to them to decide, and it is something they will likely need to experiment with over time to see what works best for them to enable the benefits. Having a team within a team was a bit confusing.

2020 209

2020 SCRUM Underperforming Technical Team Software Review 209

Scrum.org

JULY 28, 2021

As an employee of a development team, how do I know if this is the case? Let's start with a simple question for the team: The Customer . How many people are between the user and the development team? Do we ever want to invite a user to the sprint review? How do I know we are are customer obsessed company?

SCRUM 210

SCRUM Development Team Review Software Review Engineering 210

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. . See a recent blog post I wrote about this). SAFe has a cadence at the Team and Program levels.

SCRUM 113

SCRUM Development Team Review Technical Review Cadence 113

ProjectManager.com

NOVEMBER 22, 2021

The term scrum was introduced in a “Harvard Business Review” article from 1986 by Hirotaka Takeuchi and Ikujiro Nonaka. It became a part of agile when Ken Schwaber and Mike Beedle wrote the book “Agile Software Development with Scrum” in 2001.

Technical Review 483

Technical Review Prince2 Manufacturing Lean 483

Agilemania

FEBRUARY 22, 2022

Taking charge of the daily meetings, reviews, demos, and helping teams to improve are responsibilities of a Scrum Master. . Scrum Team. Coaching the team members in self-management and cross-functionality. Assisting the Scrum team focus on forming high-value increments that meet the Definition of Done .

Certification 98

Certification 2022 Development Team Review 2019 98

Scrum.org

OCTOBER 5, 2020

In this blog series I would like to address topics that relate to professional team coaching as well as Professional Scrum. In the course of becoming a Professional Team Coach, I noticed a lot of interesting topics for Scrum Masters who want to improve their coaching stance. . There are more ways to contract a team.

SCRUM 154

SCRUM Development Team Review Sustainability Agile 154

ProjectManager.com

NOVEMBER 3, 2021

Release planning lets software development teams plan better, direct their efforts more effectively and release projects incrementally, which helps the customer experience. Release planning is a great way for scrum teams to plan their sprints when working in product development. Learn More!

Agile 326

Agile Planning Software Review Software Developers 326

Scrum.org

NOVEMBER 12, 2018

In the "Scrum from the trenches" blog post series I like to address topics that I encounter in practicing Scrum in the real world, with real Scrum Teams. Sharing where theory comes into practice, what challenges teams encounter along the way and ways to help Scrum practitioners use the power of empiricism to overcome these challenges.

SCRUM 152

SCRUM Development Team Review Estimate Software Review 152

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 96

SCRUM Development Team Review Software Review Influencer 96

Scrum.org

FEBRUARY 11, 2020

Philosophy for being an outstanding team member. In another blog post, I covered how this can make your Sprint Retrospective more effective. Now let’s have a look at how this benefits your team’s Sprint Planning event. Also, some flip charts already on the walls… The team’s Definition of Done is clearly visible.

Planning 152

Planning Development Team Review Construction SCRUM 152

Scrum.org

FEBRUARY 11, 2020

Philosophy for being an outstanding team member. In another blog post, I covered how this can make your Sprint Retrospective more effective. Now let’s have a look at how this benefits your team’s Sprint Planning event. Ten minutes before the start of the event, some team members are already in the room. Same as usual.

Planning 127

Planning Development Team Review Construction SCRUM 127

Agilemania

AUGUST 21, 2022

Well, it means that you need to streamline your product development processes and reduce the amount of time wasted on red tape and unnecessary paperwork. In this blog post, we’ll be taking a look at exactly what sprints are and why you should implement them within your organization. In Jira, a sprint is represented by a sprint issue.

Software Review 98

Software Review Development Team Review SCRUM Estimate 98

Scrum.org

FEBRUARY 11, 2020

In this blog, we’ll dive deeper into the topic: “Scrum Master vs Project Manager”. If you’re having a similar question about the Product Owner vs the Project Manager, then see this blog (coming soon). Now that we have explored the Scrum Master role, let us move on to the “vs Project Manager” part of this blog.

SCRUM 211

SCRUM Prince2 Risk Management Development Team Review 211

Scrum.org

JANUARY 11, 2023

This blog post will discuss the day-to-day activities of this position and explore how these responsibilities help create successful projects. Definition of a Product Owner: A product owner is an individual who has ultimate responsibility for defining what features will be included in a product or service.

Technical Review 196

Technical Review Software Review Agile SCRUM 196

Henny Portman

MARCH 1, 2020

Scream uses the pillars of obfuscation, asymmetric information and moving targets and the following value definitions: “Courage” means accepting more work than can be done. Scream Teams appear self-organizing and cross-functional when indeed the entire show is run by the manager.

Agile 76

Agile Development Team Review 2019 Innovation 76

Wrike

APRIL 12, 2023

Defining Scrum Scrum is an agile project management methodology that enables teams to deliver high-quality software and involves regular reviews and feedback sessions. Scrum Teams typically consist of a Scrum Master, Product Owner, and development team.

SCRUM 36

SCRUM Development Team Review Software Review Project Life Cycle 36

Leading Agile

JANUARY 16, 2020

It can be easy to get swept up in discussions centered around making sure that the work being done by development teams is in sync with what the stakeholders have identified as being of the highest priority to them. Personal blog: [link]. We Need Reviews. Click here to leave us a review or post feedback.

Software Review 100

Software Review Development Team Review Consulting 100

ProjectManager.com

JUNE 2, 2022

We’ll get into the definition, illustrate product breakdown structure examples and even offer a free product breakdown structure template to give you practical experience with using this helpful flowchart. First, you need to assemble your product development team and begin the process of identifying the products in your project.

Prince2 206

Prince2 Risk Management Development Team Review Executing 206

Scrum.org

OCTOBER 2, 2018

When we say “Working Software” in the Agile Manifesto, we don’t mean just “It is working and we tested it meets our acceptance criteria and our definition of Done”. These are nice levels of transparency that are much better than just reviewing documentation of course, but they leave a lot to be desired.

Cadence 134

Cadence Development Team Review Software Review Technical Review 134

Scrum.org

JUNE 22, 2019

For these organizations, creating a Developer Culture isn’t a nice to have, it’s the only way to survive! Creating a Developer Culture isn’t a nice to have, it’s the only way to survive!”. In this blog post, I’ll share examples of how I experienced a Developer Culture. Examples of a Developer Culture.

Underperforming Technical Team 150

Underperforming Technical Team Technical Review Software Review Development Team Review 150

Scrum.org

OCTOBER 2, 2018

When we say “Working Software” in the Agile Manifesto, we don’t mean just “It is working and we tested it meets our acceptance criteria and our definition of Done”. These are nice levels of transparency that are much better than just reviewing documentation of course, but they leave a lot to be desired.

Cadence 127

Cadence Development Team Review Software Review Technical Review 127