Scrum.org

MAY 4, 2020

TL; DR: A Remote Daily Scrum with a Distributed Team. We started this series on remote agile with looking into practices and tools; we explored virtual Liberating Structures, and how to master Zoom. This eighth article now looks into supporting a distributed Development Team organizing a remote Daily Scrum.

SCRUM 168

SCRUM Agile Technical Review Development Team Review 168

Leading Answers

NOVEMBER 8, 2020

When should we be using an agile approach for our project? The agile convert might claim “Always,” just as the predictive enthusiast could scream “Never!” Agile suitability tools are nothing new. We can learn techniques for running traditional, predictive projects and adaptive, agile ones.

Agile 78

Agile 2020 Development Team Review Software Review 78

Project Pulse Journal

APRIL 17, 2024

This concept is vital across methodologies like Agile and Waterfall , where its application significantly influences project outcomes. From individual coding tasks to large-scale releases, the DoD sets the bar for quality and completeness, ensuring everyone - from developers to stakeholders - is on the same page.

Software Review 52

Software Review Development Team Review Technical Review 2024 52

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). Agile product roadmap example.

Development Team Review 148

Development Team Review 2022 Technical Review Software Review 148

Velociteach

MAY 10, 2023

More recently, the profession has grappled with two intertwined questions: Should principles or processes govern project management? Processes describe the inputs, tools, techniques, and outputs used to execute project activities. A toolkit is a collection of techniques and practices used within the project processes.

Lean 88

Lean Cadence PMI 2001 88

Scrum.org

FEBRUARY 4, 2020

“The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team.” Source : Scrum Guide 2017. 100% in advance: The Scrum Team creates a Product Backlog covering the complete project or product upfront because the scope of the release is limited.

Development Team Review 193

Development Team Review Underperforming Technical Team SCRUM Technical Review 193

Scrum.org

AUGUST 25, 2022

This has always been a huge struggle for us and most of the teams we’ve been part of. Unfortunately, many developers and development teams still burn more hours than are probably good for them. High-stress environments are also more likely to burn developers out (Sonnentag et. Burnout–depression overlap: A review.

Sustainability 178

Sustainability 2015 2014 2013 178

Scrum.org

DECEMBER 19, 2019

In 2017 I was talking to the head of the Agile Coach Group of a large bank. The birth of spreadsheet Agile adoption. Assuming that the best way of working is known, the only thing left to do is to ensure that all branches and teams work according to it. Taylor inspired spreadsheet Agile adoption. Avoid Frederick W.

SCRUM 126

SCRUM Development Team Review 2017 2019 126

Scrum.org

NOVEMBER 25, 2019

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. By the end of the Sprint Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint.

Underperforming Technical Team 200

Underperforming Technical Team SCRUM Development Team Review Agile 200

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? Communicator : The transfer of knowledge between different sites, as well as from and to the team. Data from our Scrum Team Survey may shed a light on this.

2014 211

2014 2008 Technical Review 2019 211

Scrum.org

FEBRUARY 10, 2022

Deshalb habe ich bereits 2017 eine erste Umfrage zum Net Promoter Score® des Scaled Agile Framework SAFe ® durchgeführt. Viereinhalb Jahre später habe ich diese Umfrage nun wiederholt: SAFe® hat zwischenzeitlich mehrere Iterationen durchlaufen und mehr agile Praktiker haben Erfahrungen mit diesem Framework gesammelt.

Lean 174

Lean Software Review 2022 Technical Review 174

Scrum.org

FEBRUARY 7, 2022

SAFe® has always been a controversial topic within the agile community. Therefore, back in 2017, I ran a first survey on the Net Promoter Score® of the Scaled Agile Framework SAFe®. You can sign up here for the ‘Food for Agile Thought’ newsletter and join 34,000-plus subscribers. ?? The result back then was -52.

Lean 144

Lean Software Review 2022 Technical Review 144

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 152

Underperforming Technical Team 2020 Technical Review 2016 152

Scrum.org

JULY 10, 2018

While working diligently behind feature flags, using elements of Scrum, it wasn’t clear to the stakeholders the value being delivered and how well the teams were progressing towards their end goal. A project team takes on a self-organising character as it is driven to a state of “zero information”— where prior knowledge does not apply.

Technical Review 86

Technical Review Development Team Review Engineering 2017 86

Scrum.org

FEBRUARY 8, 2020

Previously, I was involved in setting up a retail bank from scratch and in the development of mortgages solutions. During my previous job I worked intensively in tuning the agile way of working into a model for the performance organisation. . This was in late 2017. . A couple of days later he called me. scaling [1].

Underperforming Technical Team 154

Underperforming Technical Team Software Review SCRUM Technical Review 154

Scrum.org

DECEMBER 4, 2019

The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team. Source : Scrum Guide 2017. See also the detailed lists of services rendered to the Product Owner, the Development Team, and the organization by the Scrum Master as defined by the Scrum Guide.). The Sprint Planning.

SCRUM 118

SCRUM Underperforming Technical Team Development Team Review Technical Review 118

Herding Cats

APRIL 16, 2019

Management Processes (#MP). Agile Project Management (#APM). Agile Software Development (#ASD). Integrating Agile and Earned Value Management (#AEVM). Agile and Earned Value Management Bibliography of papers, books, and thesis (#Biblio). Management Processes. Project Performance Management (#PPM).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

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. This process is in essential your gateway to Agility. Core purpose of Scrum. Why is this so important?

Influencer 95

Influencer SCRUM Development Team Review 2017 95

Binfire

FEBRUARY 22, 2017

In this article I lay down the processes that you need to follow for selecting the right project management software for your business. This is not a product review article, but a guide on how to choose the right software for your needs. Visual PM tools which only support Agile or Kanban. Team Communication tools.

Software Review 119

Software Review Software Aerospace Development Team Review 119

International Institute for Learning

SEPTEMBER 20, 2022

Regarding the right size of a team, it has been experienced that a good number is around 10. For instance in the Agile Scrum Methodology [4] it is recommended to have 10 or fewer people in a team. Jeff Bezos, founder of Amazon, likes to use the “two-pizza rule” for strategy and development teams.

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52

Planio

FEBRUARY 19, 2020

However, a 2017 study found that software failures cost the U.S. Why you should start testing as early as possible during your development process. A test plan is one of the most important parts of any software development process. What are the steps for reviewing what’s been done and picking up? economy $1.7

Planning 78

Planning Software Review Underperforming Technical Team Technical Review 78

Wrike

MARCH 14, 2023

Part of the Atlassian Group, Jira originated as bug tracking software for development teams , but has since grown to encompass a number of different products. Agile teams respond well to Jira because it was built to make scrums, sprints, and Kanban methodology easy with boards, backlogs, and roadmaps.

Software Review 41

Software Review Technical Review 2006 Engineering 41

Scrum.org

NOVEMBER 2, 2018

This second post in the ‘Agile ADHD’ series from me, Sally Waters, and my husband Francis, is all about the details of how we implement Scrum at home. To see in detail how we got started and began to adapt this system, you can read my Agile ADHD blog (which lasted for the first six weeks) . Very inspirational. . Steve Trapps.

SCRUM 126

SCRUM 2018 Underperforming Technical Team Software Review 126

Gunther Verheyen

DECEMBER 22, 2017

The event serves for the Development Team to share the daily progress, plan the work for the next 24 hours and update Sprint Backlog accordingly. Development standards : the set of standards and practices that a Development Team identifies as needed to create releasable Increments of product no later than by the end of a Sprint.

SCRUM 44

SCRUM Development Team Review 2013 2016 44

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. In part two, I will be delving deeper into this topic by discussing the process of collecting and writing requirements. Hello, my name is Walter Stinnett.

Underperforming Technical Team 52

Underperforming Technical Team Technical Review Defining Project Life Cycle 52