Scrum.org

OCTOBER 19, 2022

Ultimately, the role of (top) management is to keep their business healthy and economically sustainable. SCRUM and productivity in software projects: a systematic literature review. In 14th International Conference on Evaluation and Assessment in Software Engineering (EASE) (pp. C., & da Silva, F. 2010, April).

Agile 198

Agile 2010 2013 2008 198

Herding Cats

MARCH 11, 2017

Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp. Architecting Large Scale Agile Software Development: A Risk–Driven Approach,” Ipek Ozkaya, Michael Gagliardi, Robert L.

2003 46

2003 2014 2015 2011 46

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

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

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

Binfire

APRIL 7, 2017

The Agile project management methodology has been used in the software development and IT industry for the past sixteen years, but recently it has gained wide acceptance by many number of industries and organizations. In 2001 a group of software engineers and scientists in IT industry got together and wrote Agile Manifesto.

Agile 100

Agile Technical Review Software Review Development Team Review 100

Wrike

MARCH 4, 2015

His solution is unconventional: with a huge staff of software developers at his disposal, he splits them into eighteen teams. Apply the Pareto principle to find out which 20% of your workday really matters, and learn how to work smarter to achieve sustainable work/life balance and optimum productivity. Brooks, Jr.

Software Review 53

Software Review Underperforming Technical Team Technical Review Software Developers 53

Herding Cats

MAY 8, 2016

Uncertainty of course is present in all software development work both reducible and irreducible uncertainty. Before listening to any conjecture that estimates aren't needed to make decisions in the presence of Uncertainty for software development, please read these books. Economics of Software Development.

Estimate 28

Estimate Underperforming Technical Team Software Governance 28

Leading Agile

OCTOBER 22, 2018

In the 1960s, it was considered a baseline good practice in software engineering to test your code as you wrote it. The pioneers of software development in that era were proponents of various levels of testing; some advocated “unit” testing and some didn’t, but all recognized the importance of testing code.

Software Review 75

Software Review Infrastructure Engineering Executing 75

Leading Agile

JUNE 20, 2018

But ultimately we’ll see how the idea ties back to self-organizing teams in the context of Agile software development. I can imagine some software engineers taking umbrage at that comment. We’ll soon see that the original idea of self-organizing teams doesn’t include that point.

Agile 81

Agile Defining 2001 2009 81