Scrum.org

SEPTEMBER 8, 2020

While everyone will appreciate the effort, participating in a 2-day workshop does not mean that they mastered navigating the waters of dual-track Scrum, for example. Instead, the management ought to provide the teams with goals and guidance on how to achieve these, along with funding sufficient to meet the objectives.

Software Review 205

Software Review Agile Underperforming Technical Team Development Team Review 205

Scrum.org

DECEMBER 4, 2019

TL; DR: Scrum Master Anti-Patterns. Scrum Master anti-patterns: The reasons why Scrum Masters violate the spirit of the Scrum Guide are multi-faceted. They run from ill-suited personal traits and the pursuit of individual agendas to frustration with the team itself. The Scrum Master According to the Scrum Guide.

SCRUM 134

SCRUM Underperforming Technical Team Development Team Review Technical Review 134

Scrum.org

NOVEMBER 24, 2021

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. How much time should they spend with their team or with stakeholders? For example, there are supposedly eight stances for Product Owners. Others argue that Product Owners are great when their team doesn’t need them.

2014 226

2014 2008 Technical Review 2019 226

Scrum.org

SEPTEMBER 1, 2018

In Scrum classes we often ask the attendees to draw a picture of the Scrum framework, in order learn what their current understanding of the framework is. But they also bring forward many related elements that are important or even indispensable to support the Scrum framework, but are not roles, artifacts nor events.

SCRUM 102

SCRUM Development Team Review Software Review Influencer 102

Scrum.org

NOVEMBER 25, 2019

A simple technique that I use to help the Development Team take ownership in managing their Defnition of Done. Core Purpose of Scrum. If Scrum were to be reduced to one purpose and one only, it would be the creation of a "Done" increment. One word to summarise Scrum? I'll give you a few examples: Not having a DoD.

Development Team Review 221

Development Team Review Influencer SCRUM Infrastructure 221

Project Pulse Journal

APRIL 8, 2024

Each approach establishes the development of project deliverables as influenced by the delivery cadence, defined as the number and timing of deliveries based on the type of deliverable. Project deliverables examples include daily tasks, workflows, and processes, and will vary from team to team.

Underperforming Technical Team 52

Underperforming Technical Team Cadence Development Team Review Technical Review 52

Scrum.org

NOVEMBER 9, 2020

TL; DR: Scrum Sprint Planning Checklist. Read more about why Scrum checklists are a handy tool if applied at an operational, hands-on level, reduce your cognitive load, and free up time for more relevant things. Do you want to get articles like this one from the Scrum Master Survival Guide in your inbox?

Planning 185

Planning Technical Review Software Review SCRUM 185

Project Pulse Journal

APRIL 17, 2024

This concept is vital across methodologies like Agile and Waterfall , where its application significantly influences project outcomes. In Scrum, the DoD helps ensure that each increment is potentially shippable. This helps the project team define what needs to be delivered and prevent potential scope creep.

Software Review 52

Software Review Development Team Review Technical Review 2024 52

Scrum.org

AUGUST 19, 2018

In the previous article, we have discussed how Scrum Masters need to master many things. In this article we are going to discuss one of the stances that the Scrum Master need to master, that is the facilitation stance. So we can also say that the Scrum Master is partly responsible for poor decision generated by the group of people.

SCRUM 153

SCRUM Underperforming Technical Team Software Review Influencer 153

Scrum.org

NOVEMBER 25, 2019

The Scrum Guide on 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. Source : Scrum Guide 2017. Sprint Retrospective Anti-Patterns.

Underperforming Technical Team 216

Underperforming Technical Team SCRUM Development Team Review Agile 216

Rebel’s Guide to PM

NOVEMBER 16, 2021

Fluid is award-winning PPM software that influences your whole business for the better. There is also a list of project actions, which are all created from other sources, for example, via chat or as a result of meetings. Fluid is set up to support hybrid teams out of the box. I was impressed. Read on to find out why!

Software Review 404

Software Review Development Team Review 2021 Software 404

Scrum.org

FEBRUARY 25, 2024

TL; DR: Scrum Anti-Patterns GPT Can a Custom Scrum Anti-Patterns GPT align teams with Scrum principles? 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. ?

SCRUM 197

SCRUM ChatGPT Technical Review Development Team Review 197

Scrum.org

MARCH 31, 2020

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. Especially development teams and technology firms in general have many years of experience with allowing their workforce to do their jobs from wherever and whenever they like.

Underperforming Technical Team 165

Underperforming Technical Team 2020 Technical Review 2016 165

International Institute for Learning

MARCH 29, 2023

Determining your team members may be easier than figuring out whether you need a project sponsor, a product owner, or both. You may also need to figure out how to balance project management needs and scrum master needs. This role enables the team to accomplish the work of the project. Employing people skills.

SCRUM 52

SCRUM Leadership Governance Government 52

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. Core purpose of Scrum. One word to summarise Scrum? Why is this so important? Empiricism.

Influencer 96

Influencer SCRUM Development Team Review 2017 96

The IIL Blog

AUGUST 2, 2023

The development team was devastated. In my consulting practice, I see development teams struggling with their users. We should plan our development to build small, usable components that allow users to regularly review, validate, and provide feedback on the emerging application. Leaders embrace change.

Underperforming Technical Team 78

Underperforming Technical Team 2023 Software Review Leadership 78

Scrum.org

SEPTEMBER 8, 2019

Users and domain experts influence design and code, which in turn influences users and domain experts. Ryan is a Scrum Master currently working with Agile teams in a multi-national insurance enterprise. Me : As Scrum Master, what did you do to help your team? This article is the story of such a discovery.

Artificial Inteligence 141

Artificial Inteligence Influencer SCRUM Defining 141

Henny Portman

JULY 10, 2019

The Quantifiable Added Value of Scrum is an interview with Jeff Sutherland about result-oriented organizations operating on clear and simple performance indicators (by Serge Beaumont). Security and development need to dance together, so it’s best if they both learn the steps together, right from the beginning of your agile transition.

Agile 58

Agile Development Team Review Influencer Sustainability 58

Project Pulse Journal

APRIL 26, 2024

Real-Time Collaboration - Digital project management tools facilitate instant communication and information sharing among team members, even if they are across different time zones. Develop an understanding of the cultural differences that influence work styles and communication preferences to enhance team dynamics and project success.

Technical Review 52

Technical Review Software Review 2024 PMO 52

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. Step 1: Review your product roadmap. Download This Template.

Software Review 107

Software Review Planning Technical Review Development Team Review 107

Agilemania

NOVEMBER 17, 2022

Customers will receive the product immediately, and developers will be actively committed to developing software. Continuous integration is a coding philosophy and procedure that encourage development teams to make modest changes and often check codes into version control repositories. Scrum Master. PSM) Training.

Software Review 98

Software Review Agile Technical Review Lean 98

Scrum.org

MARCH 2, 2020

TL; DR: Scrum Stakeholder Anti-Patterns. Learn how individual incentives and outdated organizational structures — fostering personal agendas and local optimization efforts — manifest themselves in Scrum stakeholder anti-patterns which easily can impede any agile transition. Common Scrum Stakeholder Anti-Patterns. The Sprint.

SCRUM 232

SCRUM Development Team Review Underperforming Technical Team Technical Review 232

Scrum.org

NOVEMBER 19, 2020

Sprint Retrospective is the last Scrum event within a Sprint. During this event entire Scrum Team- Scrum Master, Product Owner & Development Team inspects the Sprint and decides how to improve the next Sprint. Some of the questions that I really found useful: Whose knowledge, influence & support do we need?

Underperforming Technical Team 216

Underperforming Technical Team Software Review Development Team Review SCRUM 216

ActiveCollab

FEBRUARY 6, 2018

As a matter of a fact it will severely influence your own, as well as your team’s morale. He noted that this acronym should be expanded form SMART to SMARTER , by adding two additional criteria: Evaluated and Reviewed. For example, our dev team is practicing scrum.

Development Team Review 39

Development Team Review Sustainability SCRUM Influencer 39

Scrum.org

JUNE 18, 2021

At the end of this post you will have learned: How team cognition is essentially the “mind of a team”, with its own memory and perception of the world. What team cognition is and how substantial its influence is on the effectiveness of teams according to large-scale research efforts.

2010 192

2010 SCRUM 2006 Software Review 192

Digite

FEBRUARY 13, 2018

A question that I often get while speaking with people is: What is the difference between Kanban and Scrum? Value-system Influences. Both are heavily influenced by value-systems. Scrum is primarily influenced by the Agile Manifesto which describes the “Agile” value system. You will enjoy this excellent article.

Cadence 94

Cadence SCRUM Lean Underperforming Technical Team 94

Scrum.org

JANUARY 25, 2019

Welcome back to the Scrum Master blog series with yours truly. As we enter the new year, we are seeing Scrum becoming the most commonly used framework to manage complex product delivery in the industry. For example at iPrice , the company that I currently work with, we have set the bar high for the Scrum Master role.

SCRUM 192

SCRUM Consulting Closing Technical Review 192

Kiron Bondale

AUGUST 5, 2018

Scrum Masters) might be worth their weight in gold, but they are out there. Development team members are also valuable, but talent across most skill areas is available for the right price and with the right culture in place. Good agile leads (a.k.a. So if you are lucky enough to have an effective PO, retain them at all costs.

Development Team Review 136

Development Team Review 2003 Underperforming Technical Team Influencer 136

MPUG

MAY 6, 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 the last one is, if you can’t influence it, then don’t measure it. You can’t influence that project. Is it something we need to review?

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

NimbleWork

APRIL 11, 2024

Project managers can assess risks associated with each work package or task, prioritize them based on their impact and likelihood, and develop appropriate risk mitigation strategies. Review and Validate : Review the WBS with stakeholders to ensure that it accurately represents the project scope and objectives.

Software Review 52

Software Review Development Team Review Risk Management Defining 52

Scrum.org

APRIL 7, 2022

Considering just how popular the notion of fluid teams has become, I think it is important to weigh the evidence that supports it or contradicts it. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. It takes time to develop teams. This post is my attempt to do this.

Underperforming Technical Team 181

Underperforming Technical Team 2007 2006 2009 181

Project Bliss

MAY 24, 2017

Give an example of how a simple project would be handled with each. When you finish reading this post, you’ll have a better understanding of each, what each looks like when applied to a simple project, and reasons why each might be good or bad approaches for your team. The team repeats the same steps over and over.

Agile 185

Agile Software Review Underperforming Technical Team Technical Review 185

nTask

DECEMBER 3, 2020

When we talk about the large worldwide office transformations, we have two examples of people that made their companies into functional PMO, but even then, these individuals created a ton of decentralized lean PMOs and ultimately the structure mirrored the ways of a hummingbird flock.

Agile 78

Agile Underperforming Technical Team Energy Lean 78

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. They are the requirements that the development team will use to develop the solution. So, for example, here are some user stories as a customer.

Underperforming Technical Team 52

Underperforming Technical Team Technical Review Defining Project Life Cycle 52

Leading Agile

MARCH 17, 2021

And then how do we make decisions when teams are in conflict and how do we subordinate backlogs to a portfolio? If you just do Scrum, you’ll get the goodness out of it. I don’t mean Scrum. And so I did talk on the three things and then we came up with this talk. It was just why agile fails. How do we control things?

2021 62

2021 Agile Underperforming Technical Team SCRUM 62

Herding Cats

APRIL 16, 2019

The following material comes from conferences, workshop, materials developed for clients. The overarching theme is focused on defining what Done looks like, assessing progress toward Done in units of measure meaningful to the decision makers. Project Success Assessment - A checklist for assessing the processes for project success.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

AUGUST 22, 2018

This also meant developing software systems to support this effort. We were on of the first users of eXtreme Programming, long before Scrum was around and presented that early work in 2003, " Making Agile Development Work in a Government Contracting Environment, Measuring velocity with Earned Value." .

Estimate 35

Estimate Underperforming Technical Team Technical Review Software Review 35