Leading Agile

FEBRUARY 12, 2024

Mike Cottmeyer So, the question I have for you is what are those principles that make software soft and why are they so difficult to implement at any kind of scale in most organizations? That idea of big upfront design and late testing kind of got codified into a lot of our process governance around there. Chris Beale Yeah, absolutely.

Software 71

Software Underperforming Technical Team Governance Government 71

Herding Cats

FEBRUARY 9, 2018

We can estimate the total cost, total duration, and the probability that all the Features will be delivered on the program we are working for the US Government. Or ANY software project for that matter. This is the domain of Microeconomics and when applied to software development it is the microeconomics of software development.

Underperforming Technical Team 44

Underperforming Technical Team Estimate 2003 Software Review 44

Herding Cats

MAY 8, 2016

Governance drives processes in Agile at Scale. Governance can be ignored or even flaunted for small self contained teams. Organizing for responsiveness to external business drivers at scale means additional cost must be absorbed to govern in the presence of these externalities. . Economics of Software Development.

Estimate 28

Estimate Underperforming Technical Team Software Governance 28

Herding Cats

JUNE 7, 2018

This always takes us back the coupling and cohesion discussion all of us who were Software Engineers in the 1980's . This might be the actual definition of Independent fro the User Story. There is no way out of this for any non-trivial software development project. harder to understand and not reusable.

Underperforming Technical Team 32

Underperforming Technical Team SCRUM Software Engineering Risk Management 32

Leading Agile

NOVEMBER 29, 2023

I was at Viacom at the time, hired as a mobile product lead for all of the Nickelodeon brands and joining an organization, a game production and software engineering organization that was very waterfall. You need to start having the software engineers that can code the data scientists that can analyze.

Technical Review 62

Technical Review Software Review Engineering Infrastructure 62

Leading Agile

NOVEMBER 29, 2023

I was at Viacom at the time, hired as a mobile product lead for all of the Nickelodeon brands and joining an organization, a game production and software engineering organization that was very waterfall. You need to start having the software engineers that can code the data scientists that can analyze.

Technical Review 62

Technical Review Software Review Engineering Infrastructure 62

Teamweek

NOVEMBER 9, 2022

Software developers will be relieved to find Backlog , a PM tool built solely for IT and software engineering teams. It may sound outdated to most of us, but sometimes, there are good reasons to stick to on-premise software. Desktop vs. online PM software. Open-source project management software .

Software Review 52

Software Review Software Technical Review Construction 52

Herding Cats

JUNE 7, 2018

This always takes us back the coupling and cohesion discussion all of us who were Software Engineers in the 1980's . This might be the actual definition of Independent fro the User Story. There is no way out of this for any non-trivial software development project. harder to understand and not reusable.

Underperforming Technical Team 28

Underperforming Technical Team SCRUM Software Engineering Risk Management 28

Herding Cats

JUNE 19, 2017

The definition of a TPM is on page 14. . . Barry Boehm's work in “Software Engineering Economics”. Here's another simple definition of the Cone of Uncertainty: . Measure of Performance. Technical Performance Measure. Key Performance Parameters. Back to the Cone of Uncertainty. Prentice-Hall, 1981. .

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. Here's a simple definition of the Cone of Uncertainty: . 4] Defense Acquisition Guide , Chapter 4, Systems Engineering , 15 May 2013. [5] Software Engineering Economics”. Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10]

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. Here's a simple definition of the Cone of Uncertainty: . 4] Defense Acquisition Guide , Chapter 4, Systems Engineering , 15 May 2013. [5] Software Engineering Economics”. Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10]

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. Here's a simple definition of the Cone of Uncertainty: . 4] Defense Acquisition Guide , Chapter 4, Systems Engineering , 15 May 2013. [5] Software Engineering Economics”. Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10]

Technical Review 28

Technical Review Estimate 2005 Software Review 28

MPUG

JULY 16, 2021

One of the first things that we can do is that early on in the requirements definition phase, is to flush out those conscious and unconscious and undreamt of requirements that might otherwise not be stated. Performing requirements traceability analysis is an important part of software engineering.

Monitoring 52

Monitoring Controlling Underperforming Technical Team Technical Review 52

MPUG

SEPTEMBER 29, 2019

The number of software engineers is expected to triple the number of mechanical engineers this year alone. You definitely can see that Teams is starting to be the Microsoft hub for collaboration, and when you talk about integration and talk about To Do, there’s a Planner To Do integration. Leonardo Nogueira: Larry?

2019 40

2019 Technical Review Software Review Engineering 40

NimbleWork

JANUARY 2, 2025

Partnering with Greaterthan, they guide organizations in adopting self-organization, distributed leadership, and participatory governance. His work integrates anthropology, neuroscience, and adaptive systems theory, influencing global governments and industries.

Lean 105

Lean Influencer Technical Review 2025 105

Herding Cats

MAY 7, 2019

“Effort Estimation of Use Cases for Incremental Large-Scale Software Development,” Pareastoo Mohagheghi, Bente Anda, and Reidat Conradi, Proceedings of the 27th international conference on Software engineering. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B. 9, Issue 3, No.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

OCTOBER 5, 2018

The cone says the effort estimate determined in earlier phases of the project, such as the definition of the initial concepts, might differ up to four times from the final one. This variation can be explained by the fact that initial concepts do not describe the final software system accurate enough. 1, January 2011. "A 37–48, 2007.

2012 48

2012 2007 2010 2011 48

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

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." . Let's start with the obvious.

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

MPUG

OCTOBER 15, 2020

As far as I know, the value is definitely higher, and as PMI study, I think 2018, they had a study. So definitely you are also having a salary boost. Even the engineers, hardware engineer, software engineer, mechanical engineer. Now you’re thinking, how about mechanical engineer I just said.

PMI 52

PMI Certification Software Review Technical Review 52

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

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 35

Risk Management Risk Technical Review 2002 35

Leading Agile

AUGUST 20, 2018

The same rule of thumb applies to other governance reviews, as well. When all servers of a given type are generated from the same configuration script, there can’t be any question of inconsistent definitions. Another company had a major application whose logic was divided between Java code and Blaze Rules Engine definitions.

Software Review 77

Software Review Software Technical Review Development Team Review 77