Scrum.org

JANUARY 7, 2020

Do you frequently find yourself in Sprint Reviews that only consist of a PowerPoint presentation? Or entirely without users, customers and other stakeholders present? Our experience, as well as that of Scrum Masters we meet, is that the Sprint Review often takes the shape of a demo — nothing more. The Flow In A Nutshell.

Software Review 159

Software Review Development Team Review SCRUM Closing 159

nTask

OCTOBER 21, 2021

Obviously, in this fast-paced market, you are never going to perform all of these different processes by hand, and you need an incredibly effective project management software that takes care of these processes and activities for you and your team members. Another great example of a Linux project management software is OpenProject.

Technical Review 179

Technical Review 2021 Software Review Software 179

ProjectManager.com

JUNE 3, 2020

There are simple drag-and-drop tools for organizing to-do lists, planning systems for agile teams and hybrid tools for robust project management. After reviewing dozens of these tools, we’ve found that there are four specific features of a kanban tool that are must-haves for any serious user. Collaboration.

Development Team Review 290

Development Team Review Software Review Agile Manufacturing 290

Scrum.org

JULY 15, 2024

I think that a lot of people are surprised to learn that Scrum is not just for software development. Scrum was first presented in 1995 by Ken Schwaber and Jeff Sutherland. Later, the Agile Manifesto, written in 2001, identified 12 principles and 4 values which are important to the smooth operation of Agile teams.

Software Developers 194

Software Developers Software Development Software Review SCRUM 194

ProjectManager.com

JUNE 27, 2019

Scrum ceremonies are meetings that are unique to scrum teams. Scrum ceremonies ensure that everyone (the scrum master, product owner and development team) is in-sync. A sprint employs four different scrum ceremonies to ensure proper execution: sprint planning, daily scrum, sprint review and sprint retrospective.

SCRUM 230

SCRUM Underperforming Technical Team Development Team Review 2011 230

Scrum.org

OCTOBER 12, 2020

As per Scrum Guide – The Sprint Goal is an objective that will be met within the sprint by implementing the Product Backlog , and it guides the Development Team on why it is building the Increment. During the Sprint Planning , the product owner presents business objectives for the Sprint and an ordered Product Backlog.

Planning 254

Planning Technical Review Development Team Review Software Review 254

ProjectManager.com

FEBRUARY 21, 2019

A good product vision will be aspirational, offering reasons as to why the team is working on the product now, and for whom. It should motivate teams to see this not merely as another job but a mission that fulfills an important need. The product vision is also a way for a manager to stay present in the project without micromanaging.

Technical Review 295

Technical Review Development Team Review Software Review Agile 295

Scrum.org

SEPTEMBER 14, 2020

Scrum has proven time and again to be the most popular framework for software development. Given that software is eating the world , a seasoned Scrum Master is nowadays in high demand. 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

Scrum.org

SEPTEMBER 24, 2021

When I present the Scrum framework to a new team, I almost always hear someone cry out, “How can we get anything done with so many meetings?! ” The Scrum framework consists of five events (what the uninitiated refer to as meetings), three artifacts, and three roles. We can’t deliver working software in less than one month! (You

SCRUM 240

SCRUM Software Review Lean Leadership 240

Digite

MARCH 12, 2018

In my over 25+ years in the software industry, this has been an all too familiar situation! I have often wondered – doesn’t speak too well of us as software professionals! Far too many projects and teams are occupied by far too many crises all through the development/ implementation lifecycle. Our Kanban Journey.

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

ProjectManager.com

JULY 23, 2020

There are other names for virtual teams, such as “geographically dispersed teams” or “remote teams,” but they all mean the same thing: people working together without being physically together. There’s no time like the present for a crash course in virtual teams! Examples of Virtual Teams.

2019 299

2019 Software Review Development Team Review Infrastructure 299

Scrum.org

SEPTEMBER 13, 2021

Scrum has proven time and again to be the most popular framework for software development. Given that software is eating the world , a seasoned Scrum Master is nowadays in high demand. Scrum Anti-Patterns: From Product Backlog to Sprint Review. Development teams often create tasks an engineer can finish within a day.

SCRUM 233

SCRUM Underperforming Technical Team Development Team Review 2020 233

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. It also encourages everyone to review/adopt the values (in Scrum language) that can help software development teams succeed in building software. Disclaimer.

Development Team Review 93

Development Team Review Software Review Underperforming Technical Team SCRUM 93

Scrum.org

MARCH 22, 2021

Another common cause for a Scrum Team to consistently fail in meeting their forecasts is that the team’s Product Backlog items are being poorly prepared, thus making the work items difficult for the team to estimate. Trends derived from these polls are great points for discussion during a team’s Sprint Retrospectives.

SCRUM 235

SCRUM Underperforming Technical Team Development Team Review Technical Review 235

nTask

DECEMBER 8, 2020

These qualifications have evolved due to the challenges that are faced by the companies in the project management paradigm – and that too on daily basis. They will help improve the communication channels that are present in the company, resulting in improved communication and collaboration between the team leaders and project managers.

Underperforming Technical Team 158

Underperforming Technical Team Planning Development Team Review Software Review 158

Leading Agile

SEPTEMBER 17, 2020

So, what we’re looking for are cross-functional teams, clear backlog, good acceptance criteria, work broken down as small as possible, so that we can integrate the Dev Teams and QA Teams as we go and create feedback loops throughout the life of the Sprint. Each tier is focused on its own type of quality assurance.

Software Review 127

Software Review Agile Development Team Review Governance 127

ProjectManager.com

NOVEMBER 5, 2019

Similar to the waterfall methodology , the phase-gate process is a linear project management concept punctuated by stages of development followed by benchmarks for assessment. It is typically used for new product developments, software/app/website launches and business-wide changes. Phase 3: Development.

Development Team Review 163

Development Team Review Process Underperforming Technical Team Technical Review 163

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?

ChatGPT 227

ChatGPT SCRUM Underperforming Technical Team Technical Review 227

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. How to improve team dynamics? How to show servant-leadership and ‘read the room’ when you’re not physically present with the team? Things to try….

SCRUM 220

SCRUM Development Team Review Technical Review Consulting 220

Project Bliss

MAY 24, 2017

Then after completing all the work and developing the product, they hand it off to the customer. For a software project, the work in waterfall development follows a sequential order that looks like this : Requirements Gathering and Analysis . Design and Develop (Coding). The developers write the code.

Agile 185

Agile Software Review Underperforming Technical Team Technical Review 185

Scrum.org

NOVEMBER 18, 2020

The Scrum Guide 2020 is available now: Change is coming to make Scrum more accessible and inclusive beyond software development. Scrum has witnessed many applications beyond its origins of software development over recent years. The Sprint Review lost its detailed recipe on how to run the event.

2020 185

2020 SCRUM Development Team Review Software Review 185

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? Invite your manager to the Sprint Review.

Technical Review 181

Technical Review Underperforming Technical Team Development Team Review Software Review 181

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 211

SCRUM Underperforming Technical Team Software Review Development Team Review 211

Scrum.org

MARCH 4, 2019

Whatever it is we do, from the outside it looks like the majority is enjoying this new and more playful approach for software development. Once bugs come raining down we learn that DONE software does not run on 'localhost'. Scrum Masters focus on themselves and the team while doing Scrum by the book.

SCRUM 156

SCRUM Software Review Development Team Review Underperforming Technical Team 156

Scrum.org

AUGUST 1, 2022

It may suffice to move an item on the Scrum Board or Kanban Board to “Done” or “Ready for Review”, although a verbal statement is probably clearer for teams where the Scrum Board isn’t visible all the time. Many studies have found that psychological safety has a positive influence on team effectiveness (Edmondson, 2014).

2004 251

2004 2010 2009 2016 251

nTask

AUGUST 22, 2019

Some of its approaches, other than Scrum , include Extreme Programming (XP) for quality upfront building, Lean thinking for waste elimination and the Agile Unified Process (AUP) approach to developing business application software using agile techniques. The Scrum team is divided as follows: Product Owner. a Scrum Master.

SCRUM 132

SCRUM Technical Review Development Team Review Software Review 132

LiquidPlanner

SEPTEMBER 20, 2018

These teams struggle with Agile practices as business analysts author reams of business requirements only to have a development team write the user stories. Business representatives assume the product owner role but only check in with their team at the sprint review. The development team is distributed.

Agile 144

Agile Software Review Development Team Review Certification 144

Planio

JANUARY 31, 2022

That’s why a product roadmap is the backbone of every great development team. And unfortunately, too many teams treat roadmapping like just another project, leaving it behind to collect dust as they move on and start building software. Why you need a roadmap (even as an agile team). Basic product roadmap example.

Development Team Review 148

Development Team Review 2022 Technical Review Software Review 148

Scrum.org

AUGUST 17, 2020

Scrum has proven time and again to be the most popular framework for software development. Given that software is eating the world , a seasoned Scrum Master is nowadays in high demand. Though whatever the case, we can say for sure that Scrum is very popular in software development. Introduction.

SCRUM 234

SCRUM Technical Review Software Review Agile 234

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. Less handovers, closer to actual development in both time and communication distance. In Sprint Research. .

SCRUM 173

SCRUM Agile Development Team Review Software Review 173

Scrum.org

JUNE 11, 2019

And what will make your future success possible (Future~Present)? Participants agreed that “Done” software is the driver of change; software that is released to production and in the hands of users. In most of the success stories, the involvement was not limited to the Sprint Review. Done” is the driver.

SCRUM 193

SCRUM Development Team Review Software Review Lean 193

ProjectManager.com

FEBRUARY 28, 2019

The entire team is present for the sprint retrospective. That includes the Scrum Master, the product owner, the development team and everyone who is designing, building and testing the product. Although, it is not unprecedented for the Scrum team to seek outside insight and perspectives. Who’s Involved?

SCRUM 251

SCRUM Development Team Review Agile Software Review 251

Scrum.org

FEBRUARY 18, 2020

The Development Team uses the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog. The Daily Scrum optimizes the probability that the Development Team will meet the Sprint Goal. The Scrum Master is present at the Team Board.

SCRUM 203

SCRUM Development Team Review Software Review Lean 203

Scrum.org

FEBRUARY 8, 2020

THIS IS A REPOST ARTICLE DETAILING THE KEYNOTE I CO-PRESENTED AT THE LESS CONFERENCE IN 2019. Our Business Lending product is being developed by more than 20 teams spread across 3 sites. Each team contains business, IT and operations skills. Output driven development. How to bring all of this together?

Underperforming Technical Team 205

Underperforming Technical Team Software Review SCRUM Technical Review 205

Scrum.org

MARCH 4, 2019

Whatever it is we do, from the outside it looks like the majority is enjoying this new and more playful approach for software development. Once bugs come raining down we learn that DONE software does not run on 'localhost'. Scrum Masters focus on themselves and the team while doing Scrum by the book.

SCRUM 26

SCRUM Software Review Development Team Review Underperforming Technical Team 26

Scrum.org

NOVEMBER 24, 2021

Which activities can be fulfilled by others in the team, and what is needed for that? One of the reviewers of this article, Maarten Dalmijn , noted that he missed “product discovery” as a core activity in the work by Bass (2018). Maarten, who is an experienced Product Owner, added that he spends a lot of time on this with his teams.

2014 233

2014 2008 Technical Review 2019 233

Scrum.org

APRIL 27, 2020

There are some great posts out there that present a conceptual model for thinking about Sprint Goals, like this one and this one. This post concerns the development of a product that aimed to make a set of related HR-products?—?both This ranged from software for hour registration to invoicing and from recruitment to personnel planning.

Technical Review 200

Technical Review Software Review Development Team Review Infrastructure 200