Scrum.org

NOVEMBER 24, 2021

This includes training, technical support, and preparation for new releases. 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). The Sprint Review is an excellent opportunity to engage in product discovery. rather than on your own”.

2014 206

2014 2008 Technical Review 2019 206

Herding Cats

MAY 7, 2019

This blog page is dedicated to the resources used to estimate software-intensive systems using traditional and agile development methods. Cost Modeling Agile Software Development,” Maarit Laanti and Petri Kettunen, International Transactions on Systems and Applications, Volume 1 Number 2, pp. Performance Evaluation of non?Markovian

Estimate 40

Estimate Software Review Software 2012 40

Scrum.org

MARCH 22, 2023

I dove into sustainable IT and started with a ‘Planet Earth Retrospective’ for my Scrum Team, where we reviewed the Principles of Green Engineering. The sprint review showed the value they achieved for the planet, reducing an estimated 4 tons of CO2 per year. What if all Scrum Teams would do that?

SCRUM 167

SCRUM Sustainability Infrastructure Technical Review 167

Wrike

JUNE 11, 2023

Consider enrolling in relevant courses, attending workshops or conferences, or seeking mentorship from industry experts. Are you passionate about technology, healthcare, or perhaps entrepreneurship? The rapidly evolving job market and technological advancements can make it difficult to predict future career opportunities.

Technical Review 36

Technical Review Healthcare Underperforming Technical Team Software Engineering 36

Herding Cats

NOVEMBER 7, 2016

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. The Future of Systems-and Software Development. Springer International Publishing, 2016.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

MAY 10, 2019

Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods.

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

Herding Cats

MARCH 11, 2018

Microeconomics is applicable to the development is software systems. If we look at the discipline of software engineering, we see that the microeconomics branch of economics deals more with the types of decisions we need to make as software engineers or managers. Software engineering economics."

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Scrum.org

FEBRUARY 3, 2020

Software development is (generally speaking) very complex. Developing a new product requires understanding of the users, of the technologies involved and what makes something valuable (or not). Why our brain is not built for software engineering. In this post I will argue that our cognitive abilities are limited.

2002 190

2002 SCRUM 2007 2003 190

Teamweek

OCTOBER 20, 2022

You probably already know—Agile isn’t just for software developers anymore. After all, Agile projects deliver proven value in software projects: Higher profit More meaningful projects and client relationships Greater productivity Clearer communication. Buzzword alert. For example, rework or lack of team productivity.

Agile 52

Agile Technical Review SCRUM Executing 52

Herding Cats

MARCH 11, 2017

The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. The Development of Progress Plans Using a Performance–Based Expert Judgment Model to Assess Technical Performance and Risk,” Justin W. They cannot be suppressed or removed. 12, 2008.

2003 46

2003 2014 2015 2011 46

Teamweek

MARCH 30, 2022

Especially since the pandemic, many recruiters are leveraging digital technology for online job simulation tests to save on in-person expenses. Skills assessments could be used to simulate a real-life coding task, a question from a colleague, or a document review. That’s much easier for the candidate too! Why use them?

Process 52

Process Software Review Engineering Risk Management 52

Herding Cats

DECEMBER 8, 2017

It can be the needed performance of a measure - Effectiveness, Performance, Key Performance Parameter, or a Technical Performance Measures. The specifics of the Technical Performance Measures applied to inform Physical Percent Complete and the Cone of Uncertainty around the TPM are shown here. Here's a summary of these elements.

Performance Measurement 35

Performance Measurement Technical Review 2017 2008 35

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. There's only so much we can predict up front.

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

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. For technical design, there are existing designs, patterns, packages, architecture references, and similar resources.

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

Herding Cats

JUNE 19, 2017

The Cone of Uncertainty is a framing assumption used to model the needed reduction in some parameter of interest in domains ranging from software development to hurricane forecasting. The Cone of Uncertainty as a Technical Performance Measure. The Cone of Uncertainty as a Technical Performance Measure. Measure of Effectiveness.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35