Digite

AUGUST 14, 2017

Be it the “software development process” or the “employee onboarding process” or “the procurement process” – agility is rapidly becoming a cornerstone of our digital world. What are the key risks in the adoption and scaling of Kanban to drive enterprise agility? The method wars.

Agile 94

Agile Lean 2005 Risk Management 94

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 risk is created when we have not accounted for this natural variances in our management plan for the project. An aleatory risk is expressed as a relation to a value.

2003 46

2003 2014 2015 2011 46

Wrike

SEPTEMBER 29, 2022

With today’s speed of work and innovation, it’s imperative that your business finds an ideal work management software to streamline projects , optimize workflows , automate tasks , and enhance team productivity without causing burnout. . Wrike was launched in 2006 by founder and software developer Andrew Filev.

2006 36

2006 2011 Software Budget 36

ProjectManager.com

MARCH 4, 2022

The scrum methodology was developed as a response to rigid project management approaches such as the waterfall method, which didn’t adapt to the needs of agile product and software development teams. Scrum is part of agile software development and teams practicing agile. What Is the Scrum Methodology? Learn More!

SCRUM 332

SCRUM Software Review Development Team Review Underperforming Technical Team 332

Herding Cats

DECEMBER 3, 2017

The planned uncertainty not only needs to decrease over time passing, but this reduction diminishes any impacts of risk on the decision-making processes. Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. This letter states.

2007 34

2007 2012 2009 2010 34

Herding Cats

JULY 24, 2017

Shipping on time, to specifications, and within budget might be meaningless if a competitor is shipping software that has a greater value to the market. It's suggested from observations, the Cone of Uncertainty (CoU) is not a valid model of how uncertainty behaves in software development projects. Laird and M.

2007 42

2007 2012 2006 2008 42

Herding Cats

OCTOBER 11, 2016

There is a current rash of suggestions on how to improve the performance of software projects. One case of 12 projects from a large contractor of Software Intensive System (SIS) shows similar variances . I'd suggest the Principles for project success on non-trivial software efforts are universal. NASA Cost Estimating Handbook.

Performance Measurement 28

Performance Measurement Aerospace 2006 Estimate 28

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." Boehm, Barry W.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance. Prentice-Hall, 1981.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance. Prentice-Hall, 1981.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance. Prentice-Hall, 1981.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

OCTOBER 16, 2018

In ISO 15288 this is the role of the Risk Management Processes. A second Critical Success Factor is the ability to predict what will happen in the future given the model of the project's activities and risks and the alternative designed as well as emerging designs and external processes. . This is the desired outcomes model.

Aerospace 41

Aerospace Engineering 2012 2014 41

Scrum.org

APRIL 7, 2022

Kozlowski & Ilgen (2006) describe this reciprocity as “process begets structure, which in turn guides process”. Wang et al (2006) studied software teams tasked with ERP implementations and found that cohesive teams performed significantly better than less-cohesive teams. In turn, this facilitates further collaboration.

Underperforming Technical Team 173

Underperforming Technical Team 2007 2006 2009 173

Herding Cats

APRIL 4, 2019

In a recent exchange in social media, it was clear the notion of risk and the sources of risk, the consequences or risks and managing in the presence of risk was in very unclear, when it was conjectured , we can simply slice the work into small bits and REDUCE risk. . This is good, but it doesn't reduce risk.

Risk Management 43

Risk Management Risk 2003 2011 43

Scrum.org

NOVEMBER 6, 2019

I had no prior knowledge of agile back then (in 2006). The world is complex and the problems we're facing such as globalization, the climate crises, the risk democracy is in, etc requires focus, understanding, collaboration, and empathy in ways we haven't seen them before. . It's not so much about being agile.

Agile 14

Agile 2006 Software Review SCRUM 14

Resource Guru

JANUARY 27, 2023

During project collaboration, team members will also use tools such as shared documents, project management software, resource management software , and communication platforms to enable synergy between team members. That way, you’re reducing the risk of running into unnecessary conflict.

Underperforming Technical Team 97

Underperforming Technical Team 2006 Project Life Cycle Logistics 97

nTask

NOVEMBER 23, 2018

Introduced in 2006, with a major redesign in 2010, the platform serves as a single systematic and flexible solution for all the task management needs of a team. Being able to track the time associated with each and every project is one of the most critical aspects of a project management software. Issues and risks management.

2019 111

2019 2006 2010 Software Review 111

Herding Cats

APRIL 16, 2019

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Business, Technical, Systems, Risk, and Project Management Briefings and Presentations.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Planio

JULY 22, 2020

Risk Up Front: Managing Projects in a Complex World. If you’re also interested in Agile project management, pair the PMBOK with the PMI’s new Agile Practice Guide or our own Guide on How to Pick the Software Development Process that’s Right For you. Published date: 2006 (Revised edition). Author: Brett Harned.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

Wrike

AUGUST 3, 2023

While Jira has its strengths — particularly for software developers — it may not provide the full range of features, integrations, and automation a modern organization requires. If you’ve ever been part of a software development team, you’ve probably heard of Jira. But the key here is choosing carefully.

Technical Review 36

Technical Review Software Review Development Team Review Software 36

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. 61, September 2004.

Estimate 40

Estimate Software Review Software 2012 40

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.

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. Define the risks - reducible and irreducible - to each Capability and their Features.

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Herding Cats

AUGUST 22, 2018

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. If you're working on a software project with NO deadlines, then you're a very lucky person.

Estimate 35

Estimate Underperforming Technical Team Technical Review Software Review 35

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