Scrum.org

JANUARY 7, 2020

Do you frequently find yourself in Sprint Reviews that only consist of a PowerPoint presentation? For such an important part of the empirical process made possible by the Scrum Framework, the Sprint Review often receives the least attention in how it is facilitated. In this post, we share the design for a Sprint Review.

Software Review 158

Software Review Development Team Review SCRUM Closing 158

ProjectManager.com

NOVEMBER 3, 2021

If you’re working in software development, you know that the software development life cycle can often be frenetic. Product features and stakeholder requirements constantly change, and your initial product development plan might look very different as the project evolves. Product Features development.

Agile 372

Agile Planning Software Review Software Developers 372

Scrum.org

APRIL 11, 2019

I advise to start finding one person to be the single Product Owner for all teams. The other “fake PO’s” should be moved inside the development teams as subject matter experts so they can provide detailed requirements. The Product Owner should develop an inspiring vision and a plan to make it happen. Component ownership.

Underperforming Technical Team 180

Underperforming Technical Team SCRUM Development Team Review Software Review 180

ProjectManager.com

AUGUST 28, 2018

Agile has migrated from software development to touch just about every corner of the project management universe, and Scrum is one of the most popular frameworks for implementing it. Scrum Master: The Scrum expert who helps the team build the product according to the Scrum framework. The Development Team.

SCRUM 131

SCRUM Development Team Review 2016 Agile 131

ProjectManager.com

FEBRUARY 14, 2023

For that, you need online project management software. ProjectManager is online project management software that can generate customizable reports that show real-time data to help you see your progress and make more insightful decisions. Review and Revise You’re not done yet. Burn up chart example from pm.stackexchange.com.

Agile 383

Agile Estimate SCRUM Software Review 383

Scrum.org

JUNE 18, 2021

What team cognition looks like for Scrum teams, and what signs tell you whether it's there or not. What research in this area tells us about how you can design, support, and encourage teams to develop team cognition and become high-performing. Pictures of a session where we created a skill matrix with a team.

2010 231

2010 SCRUM 2006 Software Review 231

Scrum.org

FEBRUARY 25, 2024

Scrum Anti-Patterns GPT’s Answer Organizational issues often lead to Scrum anti-patterns that can hinder the effectiveness and efficiency of Scrum Teams. Reassigning Team Members : Frequently moving team members between Scrum Teams disrupts the building of trust and undermines the stability and effectiveness of teams​​.

SCRUM 226

SCRUM ChatGPT Technical Review Development Team Review 226

Scrum.org

NOVEMBER 18, 2020

Scrum is still about a cross-functional team of people collaborating closely with one another and their stakeholders. As a team, they create and deliver valuable and useful Increments every Sprint. . What has changed[2]: Less prescriptive, simpler language and removal of software-specific terminology.

2017 252

2017 2020 SCRUM 2005 252

Project Bliss

MAY 24, 2017

In a waterfall approach all planning is done up front, and then the team executes according to the plan. A project manager leads the effort and works closely with the team to plan and execute the project. The team generally completes work in one phase before moving on to the next. Design and Develop (Coding).

Agile 185

Agile Software Review Underperforming Technical Team Technical Review 185

Scrum.org

OCTOBER 12, 2020

On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. When a weak Development Team meets a commanding Product Owner, focusing on shipping new features, the team may end up as a feature factory, churning out new code while neglecting the technical foundation.

SCRUM 234

SCRUM Underperforming Technical Team Technical Review Software Review 234

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. And it is closely linked to the development of schedules and cost plans. Best Resource Management Software of 2021. Resource risks are not assessed. Checklists.

Underperforming Technical Team 158

Underperforming Technical Team Planning Development Team Review Software Review 158

Moira Alexander

JANUARY 12, 2017

Although Incremental software development methods go as far back as 1957, agile was first discussed in depth in the 1970s by William Royce who published a paper on the development of large software systems. These developers gathered together to discuss lightweight development methods based on their combined experience.

Software Review 100

Software Review Technical Review Development Team Review Agile 100

Scrum.org

MAY 19, 2020

From a distance, all seems well as Scrum Teams appear to go through the motions of the Scrum Framework. Sprint Planning takes place at the start of the Sprint, the Daily Scrum once every 24 hours, a Sprint Review, and Sprint Retrospective at the end of the Sprint. The four symptoms are all closely connected. It’s All Connected.

SCRUM 245

SCRUM Software Review Development Team Review 2020 245

Scrum.org

SEPTEMBER 10, 2019

Software developers are mostly guys, happy to work by themselves at night in dark rooms. And they turn coffee, cola and pizza into code. To be honest, the longer I have worked in software development the more wrong this stereotype feels to me. Collaborating closely means working with others, not only near others.

Development Team Review 138

Development Team Review Technical Review Software Review SCRUM 138

Scrum.org

JUNE 22, 2019

For years, I’ve fulfilled the role of Scrum Master for many different organizations and Scrum Teams. These teams were mostly focused on software development. These organizations were able to attract the smartest developers and create products customers loved. That’s not going to be a technical perspective.

Underperforming Technical Team 184

Underperforming Technical Team Technical Review Software Review Development Team Review 184

Scrum.org

NOVEMBER 7, 2018

SAFe's approach to product ownership is that scale is achieved by splitting the product ownership role between Product Management, which is more like the classic Scrum Product Owner, and the Product Owner, which is indeed more like a proxy or technical product owner working more closely with teams.

SCRUM 170

SCRUM Development Team Review Technical Review Cadence 170

TrustRadius Project Management

FEBRUARY 21, 2019

Making this decision can get heated due to the two major development methodologies at play. In simple terms, a development methodology determines how the actual work of development is organized and acted on. The two main development methodologies are the waterfall methodology and the agile methodology.

Software Review 132

Software Review Agile Development Team Review Software Developers 132

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. This ties closely into research on team cognition and cross-functionality. Closing words. Furuyama, T.,

2004 251

2004 2010 2009 2016 251

Scrum.org

NOVEMBER 9, 2020

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.” Ask the team members to focus on moving tickets to “Done” before starting work on new tickets.

Planning 224

Planning Technical Review Software Review SCRUM 224

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

MARCH 18, 2020

On November 22nd, 2019, I gave the closing keynote at Scrum Deutschland, a talk called ‘The Four Things You Do To Prevent Value Delivery.’ In my research, I found many issues throughout the development process, but one stuck out in particular. Background. I spent many interviews trying to find out who was accountable for things.

Technical Review 189

Technical Review Underperforming Technical Team Software Review Development Team Review 189

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 209

SCRUM Underperforming Technical Team Software Review Development Team Review 209

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 155

SCRUM Software Review Development Team Review Underperforming Technical Team 155

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

JANUARY 29, 2024

( Japanese version・日本語版 ) When picturing an effective and truly agile product development team, one often imagines a software development team, pushing some software to production every day, maybe multiple times a day, ala Amazon. We developed two strong partnerships with customers early on.

Agile 208

Agile Technical Review Underperforming Technical Team Development Team Review 208

Scrum.org

FEBRUARY 21, 2023

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. Background : As the “Manifesto for Agile Software Development” states, it is mainly about adaptability over following a plan.

ChatGPT 172

ChatGPT Development Team Review Technical Review SCRUM 172

Scrum.org

APRIL 7, 2022

Team cognition is similar in the sense that the entire team can be thought of as a body, where each member (the limbs) has to learn how to coordinate their work effectively to move forward. This shared understanding is captured in the “team mental models” that drive team cognition. It takes time to develop teams.

Underperforming Technical Team 202

Underperforming Technical Team 2007 2006 2009 202

Binfire

DECEMBER 11, 2023

Online assessment tests have become inseparable parts of every organization, and their vital role has increased over the past couple of years. However, establishing a successful online assessment test is a challenging undertaking. This blog post will discuss how project management principles can improve online assessment results.

Development Team Review 78

Development Team Review Technical Review Software Review Monitoring 78

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. Also, having just one Scrum team is rare unless youre working for a startup in its infancy. Most of the time, multiple teams develop products.

SCRUM 167

SCRUM Technical Review Software Review Innovation 167

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 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 164

Technical Review SCRUM Software Review Defining 164

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

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

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 does working remotely impact the collaboration with the Development Team? For example, the Daily Scrum is attended by the Development Team only.

SCRUM 220

SCRUM Development Team Review Technical Review Consulting 220

Scrum.org

FEBRUARY 15, 2020

Depending on the number of variables and variability within those variables, it is essential for teams or leaders to adapt their environment and style of decision making. Similarly, Sprint Backlog which is owned by the development team gives the reality of ongoing work every day. Sprint Review - 4 hours.

SCRUM 223

SCRUM Development Team Review 2012 Technical Review 223

Planio

MAY 8, 2023

On average, IT projects come with more complexity and risk, and can quickly fall to pieces without proper due diligence, management, and leadership. However, as IT projects often require a deeper understanding of technology, many IT PMs have a background in software development or IT support. And that’s no simple job.

Technical Review 78

Technical Review Software Review Development Team Review Infrastructure 78

Scrum.org

JANUARY 11, 2023

This involves assessing the needs of stakeholders, understanding customer requirements, and creating user stories that will help guide development. Improved team collaboration and communication is also achieved since everyone has clear roles and responsibilities which helps streamline decision-making processes.

Technical Review 209

Technical Review Software Review Agile SCRUM 209