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. We collected the data through our Scrum Team Survey. We worked with Prof.

Agile 197

Agile 2010 2013 2008 197

Scrum.org

JULY 11, 2022

Thus, giving birth to a new kind of hybrid technical profile that could nail any aspect of the product development. Does the Scrum Guide give some direction? It does indeed: “ Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint. ” [1]. Is this the right solution?

Software Review 142

Software Review Engineering Technical Review SCRUM 142

Agilemania

MARCH 3, 2022

Scrum is a lightweight framework through which people can address complex problems while productively and creatively delivering products of the highest quality. . Scrum is based on 3 pillars of empirical process control that are difficult to master for many teams. Scrum has 3 roles that are central to its success-.

Certification 52

Certification Lean Development Team Review Engineering 52

Herding Cats

NOVEMBER 7, 2016

And the same process is applied to the Scrum development processes on those projects. . The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ‒ Steve McConnell.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

MAY 7, 2019

Effort Distribution to Estimate Cost in Small to Medium Software Development Project with Use Case Points,” Putu Linda Primandari and Sholiq, The Third Information Systems International Conference, Procedia Computer Science, 72, pp. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B.

Estimate 40

Estimate Software Review Software 2012 40

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. Software Engineering Institute, January 1996. De Meyer, C. Loch, and M.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

JUNE 7, 2018

The direction of influence from one element to another is captured by an arrow in place of a simple link. This always takes us back the coupling and cohesion discussion all of us who were Software Engineers in the 1980's . There is no way out of this for any non-trivial software development project.

Underperforming Technical Team 32

Underperforming Technical Team SCRUM Software Engineering Risk Management 32

Herding Cats

MAY 11, 2019

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. IEEE Transactions on Software Engineering , Vol.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

JUNE 7, 2018

The direction of influence from one element to another is captured by an arrow in place of a simple link. This always takes us back the coupling and cohesion discussion all of us who were Software Engineers in the 1980's . There is no way out of this for any non-trivial software development project.

Underperforming Technical Team 28

Underperforming Technical Team SCRUM Software Engineering Risk Management 28

Epicflow Blog

MAY 14, 2019

Develop Your Leadership Skills. Varun Maheshwari , a Scrum Master at Telstra, says to “avoid project based thinking and start product thinking, have tight & fast feedback loops, make teams really autonomous, let team members talk to real customers so that they can understand domain & customer needs better, etc.

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75

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. And the last one is, if you can’t influence it, then don’t measure it.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

Herding Cats

JANUARY 23, 2019

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. This also meant developing software systems to support this effort. Rarely are software engineers working on science experiments. Almost impossible?

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

Herding Cats

FEBRUARY 9, 2019

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. This also meant developing software systems to support this effort. And money in the bank is what software development is about.

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Leading Agile

JUNE 20, 2018

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. But ultimately we’ll see how the idea ties back to self-organizing teams in the context of Agile software development. Let’s keep looking.

Agile 102

Agile Defining 2001 2009 102