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

Agilemania

DECEMBER 13, 2021

The groundwork for SAFe was formed in 4 knowledge areas – agile software development, lean product development, systems thinking, and DevOps. Code Quality. Spotify: Spotify came into being in 2012. In the Scaled Agile Framework, every team member works diligently. Architecture and Design Quality.

Agile 98

Agile Lean Software Review Technical Review 98

Wrike

MAY 23, 2023

Together, we have developed a unique quality control system for Wrike, our lovely project management platform, allowing us to deploy product code to production more quickly and without bugs. As our client base grew, so too did our responsibility to ensure high-quality product code. But he was wrong — Team Sky won in just three.

Engineering 36

Engineering Underperforming Technical Team Controlling Software Review 36

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

Herding Cats

MAY 10, 2019

Risk Management is essential for development and production programs. Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. IEEE Transactions on Software Engineering , Vol. Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003.

Risk Management 38

Risk Management Risk Technical Review 2002 38

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 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

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

Digite

JANUARY 7, 2018

Successful Evolutionary Change for Your Technology Business. This is the original book where David Anderson first laid down the definition of and guidance to the Kanban Method for software and knowledge work. 31 pages, ET to read: 50 min, Published July 19th, 2012 by Lean-Kanban University). By David J Anderson. By Mike Burrows.

Lean 79

Lean Software Review 2010 2014 79

Scrum.org

FEBRUARY 25, 2020

When I started using Scrum as a software developer back in 2007 I noticed that this new ways of working really worked, then I decided to learn more about and I became a Scrum Master in 2012 and in 2015 I started to teach Scrum, overcoming my fear of public speaking. I will explain the peer review at the end of this article.

2017 172

2017 2018 2016 SCRUM 172

Leading Agile

JUNE 18, 2018

Defensive programming consists of learning and using guidelines for software design and coding that tend to minimize the frequency and severity of problems in production. The day came when the software community more-or-less forgot about defensive programming. I guess that worked out okay for a generation of developers.

Software Review 81

Software Review Underperforming Technical Team Technical Review Artificial Inteligence 81

Scrum.org

FEBRUARY 15, 2020

In the case of product development, there are a number of variables like people, process, technology, cultures, geographies, tools, skills, relationships, etc. In the movie Avengers (2012), The Mind Stone allows the user to control the minds of others and can control what they do. Sprint Review - 4 hours. to name a few.

SCRUM 168

SCRUM Development Team Review 2012 Technical Review 168

The IIL Blog

APRIL 27, 2018

To this end, expenditures that are reviewed to ensure that a team will function optimally might include factors such as: Web-based platforms for collaboration, i.e., WebEx or GoToMeeting. Resources: Number of participants, software, and systems required, facilities, etc. Webcam equipment for real-time video conversation.

Software Review 121

Software Review 2004 2012 PMI 121

Leading Agile

SEPTEMBER 24, 2018

I frequently read and hear that software developers must take care to deliver the right solutions. The Developers Who Don’t Do Anything. I would observe lack of preparation is a cause of poor quality software. It tends to lead people to copy and paste code from StackOverflow. It’s true. Not My Job.

Software Developers 79

Software Developers Software Development Software Review Software 79

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

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

Herding Cats

OCTOBER 24, 2018

But before going further, let's establish the definitions we need to understand and apply Root Cause Analysis needed to discover the corrective and preventive actions to increase the probability of project success - especially Software Project Success. What factors lead to software project failure?” All for the want of a nail.

2014 45

2014 Aerospace 2011 2013 45

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

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

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. Thesis, University of Southern California, August 2012.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Runrun.it

OCTOBER 1, 2019

The concept originated from software development companies, who found the traditional method of project and workflow management was stifling in many situations. The agile organization and the agile squad. The agile squad is the smallest unit in the agile organization — multiple agile squads are collectively called a tribe.

Agile 20

Agile Software Review Leadership Technical Review 20