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.

2003 46

2003 2014 2015 2011 46

Digite

JUNE 13, 2018

Anderson best articulated its application to software development, in 2013, in the foundational book Kanban: Successful Evolutionary Change for Your Technology Business, and its adoption hasn’t been as universal as Scrum’s during the early days of Agile software development. Creating Your First Kanban Board.

Agile 110

Agile Technical Review Cadence Software Review 110

LiquidPlanner

NOVEMBER 2, 2017

Drawing from his years leading technology projects at Microsoft, Berkun offers readers field-tested philosophies and strategies for defining, leading, and managing projects. If you’re leading technology projects, this is a must-read. Cost: Coursera: Agile Development Specialization. Harvard Business Review. Cost: $6,570.

Technical Review 113

Technical Review 2018 Underperforming Technical Team Certification 113

Wrike

MAY 23, 2023

A year later, in 2013, they succeeded again. The second principle is to define reference points or metrics for collecting statistics and determine how they will behave in the process of technical experiments. We decided to start from the last stage — code review — which, due to the human factor, might be viewed as a bottleneck.

Engineering 36

Engineering Underperforming Technical Team Controlling Software Review 36

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

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). This is due to many reasons. 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”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). This is due to many reasons. 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”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). This is due to many reasons. Prentice-Hall, 1981.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Project Management Hacks

AUGUST 4, 2016

In 2013 , the company delivered 1.5 Through many discussions with my husband – who works in software development – I discovered an interest in the technology field. For further insight on Leigh’s entry into project management, read her blog post: How I Made the Move to IT Project Management With No Technical Experience.

2013 28

2013 2003 Technical Review 2010 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

Scrum.org

AUGUST 3, 2020

Dependencies are an epidemic in software development. Sutherland, Scrum Guide, 2013. Thing we hear (or say): Organizational Design: My team is mostly back-end; we rely on another team for the (fill in with any component of software – front end enhancements, database layer, integration, API). Scrum Master or Tech Manager.

Underperforming Technical Team 238

Underperforming Technical Team Technical Review Software Review Development Team Review 238

Scrum.org

APRIL 7, 2022

Wang et al (2006) studied software teams tasked with ERP implementations and found that cohesive teams performed significantly better than less-cohesive teams. However, several studies show that cohesion positively impacts performance only in later stages of team development (e.g. Bradley et. Or if these processes can be fast-tracked.

Underperforming Technical Team 167

Underperforming Technical Team 2007 2006 2009 167

MPUG

APRIL 29, 2020

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. Today’s session is eligible for one PMI PDU in technical category and the MPUG activity code for claiming this session is on the screen now. Kyle: More on Oliver.

Estimate 52

Estimate Software Review Risk Management Risk 52

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

Wrike

NOVEMBER 7, 2018

Project Management Software & Tools. Keys to Project Success: 48% say the team’s technical skills. Lean & Test Driven Development (TDD) – 11%. Feature Development Driven – 9%. Dynamic Systems Development Method – 3%. Technology. Project Management Software & Tools. 2% — Other. [6].

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

Workzone

AUGUST 4, 2021

This list of alternatives for Asana the project management software will help you identify which project management software you should be using. We’re going to share the top Asana alternative, Workzone, pros and cons of Asana, and 24 other software solutions so you can decide which option is worth researching further.

2021 26

2021 Software Review Technical Review Underperforming Technical Team 26

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. Chakraborty and K.

Estimate 40

Estimate Software Review Software 2012 40

MPUG

OCTOBER 9, 2019

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. Today’s session is eligible for one PMI PDU in the technical category and the code for claiming today’s session is on the screen now.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

Leading Agile

DECEMBER 17, 2018

I didn’t realize James Bond was into software development. I didn’t really expect anything to come of the tweet, and I was a little surprised at the responses. For instance: This surprised me in a couple of different ways. Why would anyone think import statements had any effect on class loading?

Underperforming Technical Team 67

Underperforming Technical Team Software Review 2008 2013 67

Herding Cats

NOVEMBER 5, 2018

In a previous post, Why Johnny Can't Estimate , mentioned some resources for estimating, the principles of business and technical management that demand estimates be made to make decisions, and background on the sources of uncertainty, that create risk, that require estimating to increase the probability of project success. taken from [3]).

Software Review 34

Software Review Technical Review Estimate Software Developers 34

Herding Cats

JUNE 21, 2016

Here's another trail being ridden by our son at Nationals in 2013. Stability is a relative term, depending on speed, terrain, skill, risk taking tolerance, experience, technical equipment, and other intangible factors. The notion of Control is missed used in software development projects. What's coming due?

Controlling 42

Controlling Technical Review Estimate 2013 42

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

MPUG

NOVEMBER 14, 2019

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. PMI PDU use in the technical category. And to be honest, I haven’t used it since 2013. You may watch the live recording of this webinar at your convenience.

2013 40

2013 Finance 2007 Software Review 40

International Institute for Learning

SEPTEMBER 20, 2022

Managing a team is definitely something really difficult because in addition, for instance, to the technical complexity of the topic, there is the challenge to coordinate people with different personalities, knowledge, background and even culture with the purpose of making the team work in an efficient way. Schwaber, K. Hackman, J.

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52

Herding Cats

SEPTEMBER 19, 2018

In this case, the Business as Usually ranges is -5% for low and +10% for a high around the most likely value for the duration, cost, or some technical performance parameter. The business as usual, but with some technical processes get a bit wider. Flight software is always an issue where we work, so those ranges are wider even more.

Technical Review 43

Technical Review 2010 Estimate Software Review 43