Scrum.org

MAY 17, 2022

The first intuition of many Scrum Masters?—?including I have a hunch that this single observation alludes to a more persistent pattern across Scrum Masters. Namely, that Scrum Masters are often more focused on the quality of the process than on the value of the outcomes. So what do Scrum Masters do most of their time?

SCRUM 184

SCRUM 2021 Software Review 2017 184

Scrum.org

OCTOBER 29, 2023

The essence of DevOps lies in its conceptual foundation, born out of software engineering. It's about understanding the impact of accelerated processes on our engineering systems and the way we design and approach our products. It's about leveraging these tools to support the idea of DevOps, not letting the tools define it.

Software Engineering 143

Software Engineering Lean Engineering Influencer 143

Scrum.org

JANUARY 28, 2024

Your single best investment to improve your professional standing; order the Scrum Anti-Patterns Guide book now! ? Brooks’ Law Frederick Brooks stated in his 1975 book The Mythical Man-Month: Essays on Software Engineering that “adding manpower to a late software project makes it later.” edition ! ?

Agile 173

Agile Technical Review Sustainability Software Engineering 173

Scrum.org

OCTOBER 19, 2022

And we share results from our own analyses based on actual data from stakeholders and Scrum teams that we collected through the Scrum Team Survey. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. The second term I’d like to define is Agile or agility.

Agile 205

Agile 2010 2013 2008 205

Scrum.org

JANUARY 31, 2024

Meistern Sie Scrum mit Leichtigkeit ; bestellen Sie jetzt das Scrum Anti-Patterns Guide Buch — es ist ab sofort verfügbar! ? Agile Gesetze: Brooks’sches Gesetz Frederick Brooks konstatierte 1975 in seinem Buch The Mythical Man-Month: Essays on Software Engineering , dass “adding manpower to a late software project makes it later.”

Agile 171

Agile Engineering Innovation SCRUM 171

Project Pulse Journal

APRIL 15, 2024

Exploring Agile methodologies provides teams with flexible, efficient, and collaborative approaches to software development and project management. Beyond Scrum , several Agile frameworks were developed to address the unique needs and challenges of projects and teams.

Software Review 52

Software Review Technical Review Agile SCRUM 52

Scrum.org

NOVEMBER 24, 2021

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. From our own quantitative research with 1.200 Scrum Teams , we know that teams are more effective when they are more aware of the needs of their stakeholders. The Scrum Guide seems pretty clear about what Product Owners are accountable for.

2014 213

2014 2008 Technical Review 2019 213

ProjectManager.com

JULY 31, 2019

So, we’ve hinted at the Agile Manifesto long enough—let’s define it. The following agile principles are what define an approach as agile. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. However, they can jump in as needed to help resolve issues.

Agile 290

Agile 2001 Software Developers Software Development 290

Project Pulse Journal

APRIL 17, 2024

It can be your reality with a well-defined DoD. In Scrum, the DoD helps ensure that each increment is potentially shippable. It defines what it means for a user story or sprint to be complete, ensuring that all scrum team members understand and meet the required quality benchmarks before proceeding.

Software Review 52

Software Review Development Team Review Technical Review 2024 52

LiquidPlanner

JANUARY 18, 2023

The principles are more detailed (and more industry specific), but still steer largely clear of defining processes or practices. No change in engineering practices. This one applies specifically to software engineering teams.) Software teams can expect to do some things differently.

Fractional VPE 148

Fractional VPE Agile Software Review 2001 148

Scrum.org

MARCH 11, 2020

After covering the Scrum Master and the Product Owner, this article addresses Development Team anti-patterns, covering all Scrum Events as well as the Product Backlog artifact. The Role of the Development Team in Scrum. Source : Scrum Guide 2017. . TL; DR: Development Team Anti-Patterns.

Development Team Review 223

Development Team Review Underperforming Technical Team Software Review Technical Review 223

Scrum.org

JULY 7, 2020

From the long list of observation, heuristics, and mental models in psychology, organizational design, or software engineering, I pick six “agile laws” that seem to be particularly relevant in this area of distributed agile teams: Conway’s Law. Remote Agile (Part 1): Practices & Tools for Scrum Masters & Agile Coaches.

Technical Review 134

Technical Review Agile Software Review Software Engineering 134

The Strategic Project Manager

DECEMBER 9, 2022

Feature-driven Development (FDD) is one of several agile methodologies or approaches (some other popular ones include Scrum , XP , DSDM, and Crystal ). FDD best practices are derived from good software engineering practices. Developing by feature – The team needs to determine how to define features.

Agile 52

Agile Lean SCRUM Software Engineering 52

Binfire

AUGUST 28, 2019

A defining feature of Agile projects is self-directed teams, although sufficient support should be provided to the team during each development cycle. The manager or the scrum master should only interfere if things go off course. What is the difference between Agile and Scrum? Who is the product owner in Scrum?

Agile 60

Agile Technical Review Sustainability Software Review 60

Redbooth

APRIL 26, 2018

The model has been favored by software engineers for its efficacy and flexibility, and it’s beginning to catch on in agencies and startups. Borrowing from Scrum methodology, an agile team has three main roles : Product Owner : An executive or key stakeholder who leads the project with vision.

Agile 128

Agile Technical Review Software Review Cadence 128

Binfire

AUGUST 27, 2017

The Agile project management methodology has been used by software engineers and IT professionals for the past sixteen years. In the late twenty century, many software engineering researchers in academia were studying the disturbing fact that most software and IT projects finish late or fail to finish at all.

Agile 97

Agile Technical Review Software Review Development Team Review 97

Epicflow Blog

MAY 14, 2019

Christine Basson , a Project Director at INEOS, says that you should “never underestimate the power of a well defined business case. Poorly defined business objectives are translated into a poorly defined project, lots of changes, [and an] unstable project platform. Facts and Fallacies of Software Engineering by Robert L.

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75

Herding Cats

JUNE 7, 2018

The interdependencies e well defined, so making a User Story Independent can take place only to the minimal level that a User Story is dependent of other User Stories for collected data, processing that data, and producing data to be collected and processed by other User Stories. Highly coupled have program units dependent on each other.

Underperforming Technical Team 32

Underperforming Technical Team SCRUM Software Engineering Risk Management 32

Binfire

APRIL 7, 2017

In the late twenty century many software engineering researchers in academia were studying the disturbing fact that most software and IT projects finish late or fail to finish at all. In 2001 a group of software engineers and scientists in IT industry got together and wrote Agile Manifesto. Agile Roadmap to value.

Agile 100

Agile Technical Review Software Review Development Team Review 100

Teamweek

OCTOBER 20, 2022

When you’re leading an agency providing marketing, web development, branding, or software engineering—your success is defined by creativity. Scrum vs. Kanban —what’s a better Agile method for us? Next, the scrum master along with the team breakdown the chosen outcomes into tasks. Enhances creativity.

Agile 52

Agile Technical Review SCRUM Executing 52

Herding Cats

JUNE 7, 2018

The interdependencies e well defined, so making a User Story Independent can take place only to the minimal level that a User Story is dependent of other User Stories for collected data, processing that data, and producing data to be collected and processed by other User Stories. Highly coupled have program units dependent on each other.

Underperforming Technical Team 28

Underperforming Technical Team SCRUM Software Engineering Risk Management 28

Herding Cats

MAY 10, 2019

Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. Defining Uncertainty in Projects ? Software Engineering Institute, January 1996.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. Defining Uncertainty in Projects ? Software Engineering Institute, January 1996.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Leading Agile

JUNE 20, 2018

So, it isn’t strictly necessary for the authors of a manifesto to define terms or express things precisely. The Scrum Alliance, an organization that supports an Agile-aligned method known as Scrum, offers an explanation of self-organizing teams , written by Nitin Mittal. is working toward meeting their emerging vision.

Agile 81

Agile Defining 2001 2009 81

PM Basics

APRIL 24, 2018

The main phase of a project is implemented with Scrum Framework. Here you need to define what is the goal of a project, and it’s success criteria. At least you need to define the key information that it has. Here is the truth: Many software development vendors develop a custom project management approach. Interviews.

Software Developers 67

Software Developers Software Development Software Review Software 67

Herding Cats

JUNE 12, 2018

At a minimum, at the end of every week, a Scrum team assess physical percent complete at the end of the Sprint. The link to the quote in the original book can be found here, Software Engineering and Metrics. Software engineering economics." IEEE Transactions of Software Engineering, 1 (1984): 4-21.

Underperforming Technical Team 40

Underperforming Technical Team Software Engineering Estimate Software Developers 40

Herding Cats

JUNE 12, 2018

At a minimum, at the end of every week, a Scrum team assess physical percent complete and updates their estimate to complete in some field in the Scrum development system. Same debunking from the Gartner Survey - no Root Causes of those poor performance numbers, undefined sampling processes, not defined population statistics.

Underperforming Technical Team 28

Underperforming Technical Team Software Engineering Estimate Development Team Review 28

Herding Cats

AUGUST 27, 2017

After having worked for outsourcing, consultancy and product companies I believe that creating a place where people really trust each other is easier when software engineers and stakeholders are both part of the same organization. The Product Manager is not always the same as the Scrum Product Owner.

Estimate 46

Estimate Software Review Underperforming Technical Team Technical Review 46

MPUG

MAY 18, 2022

A lot of people don’t like that, but whatever your scrum team decides to do is right for your team. Another way that you may want to use Excel with your work, the reports that Microsoft uses are not what scrum teams and Agile teams are used to seeing. We’re using the built in priority field, define the way we want it.

Agile 59

Agile Underperforming Technical Team Software Review Cadence 59

Herding Cats

FEBRUARY 9, 2019

This also meant developing software systems to support this effort. We were one 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 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Herding Cats

JANUARY 23, 2019

This also meant developing software systems to support this effort. We were one 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." . Let's start with the obvious.

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

MPUG

MAY 6, 2021

I actually got my degree in software engineering and moved up into project management like a lot of us did back in the day. Individual contributor team, lead section, lead project manager, program manager, director of engineering. You got three scrum teams working on this project. By education and training.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

Teamweek

NOVEMBER 9, 2022

Agile PM software comes with features for: Backlog management Agile estimation tools Sprint planning Work-in-progress limits Burn-down charts. And other features that help implement Agile practices for Scrum and Kanban methods. Do they define their processes using the same language? Creative and marketing PM software.

Software Review 52

Software Review Software Technical Review Construction 52

MPUG

OCTOBER 15, 2020

So you have master in Scrum, or master in Kanban or like a professional in Lean. Then of course, Scrum Masters, Kanban Flow Masters They can also go for this certification. Even the engineers, hardware engineer, software engineer, mechanical engineer. Life doesn’t work like that.

PMI 52

PMI Certification Software Review Technical Review 52