Herding Cats

DECEMBER 16, 2017

The estimating of software development is both straightforward and complex. Here are some resources that will provide guidance to produce credible software development estimates, in both traditional and agile domains. Software Cost Estimation with COCOMO II , Barry Boehm, et. Don't hear one? Prentice Hall, 2000.

Software Developers 46

Software Developers Software Development Estimate 2006 46

Gunther Verheyen

APRIL 24, 2020

Apparently, it is easy to get stuck at interpreting the rules of Scrum. In the publication “ Moving Your Scrum Downfield ” I have described the six essential traits of the game to help you get unstuck and up your game. These six essential traits are indicative of Scrum coming to life. Every case of Scrum is unique.

SCRUM 110

SCRUM 2003 2010 2013 110

Digite

JANUARY 7, 2018

Several good books have been written on Kanban and its application to various business processes, especially to Scrum, since David Anderson published his original Kanban “blue book”. 262 pages, ET to read: 4 hours, Published April 7th, 2010 by Blue Hole Press). Successful Evolutionary Change for Your Technology Business.

Lean 79

Lean Software Review 2010 2014 79

Scrum.org

APRIL 7, 2022

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. As we will see below, current scientific models for team formation underscore the need for time and frequent interaction to allow teams to develop the tissue that makes them high-performing. Or if these processes can be fast-tracked.

Underperforming Technical Team 155

Underperforming Technical Team 2007 2006 2009 155

Scrum.org

MAY 26, 2020

Christiaan and Barry are both Professional Scrum Trainers (PST) with Scrum.org, dedicated early adopters of Liberating Structures, and co-authors of the upcoming Zombie Scrum Survival Guide. Both are Professional Scrum Trainers and Liberating Structures enthusiasts. Also, they are co-authors of the upcoming Zombie Scrum book .

Agile 97

Agile 2004 SCRUM Software Developers 97

MPUG

JANUARY 4, 2021

I’d like to begin by sharing a brilliant quote that puts the latest project management fashion, Agile, into humbling perspective: “ A Waterfall project is just an Agile (Scrum) project with one huge sprint! For at least twenty years and counting, the world around us has become more and more software driven, and, as a result, more digital.

Artificial Inteligence 122

Artificial Inteligence Critical Chain Underperforming Technical Team Agile 122

Scrum.org

JUNE 5, 2019

It makes me wish I could’ve experienced that with a Development Team”. This is what another Scrum Master told me after we took turns during a recent training to share a success story about a Development Team. What does this say about Development Teams out there? Agile software development started with developers.

SCRUM 138

SCRUM 2002 2003 2001 138

Digite

MARCH 12, 2018

Most people, as well as me, are used to Scrum (or more likely Zombie-Scrum or Scrum-But ), but I believe it is too early to do proper Scrum here. Or rather one column per stage for the tasks (i.e., “in development”, “in testing” etc.)? In the usual Scrum process, the P.O.

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

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. A versatile project management software equipped with an intelligent toolset that caters perfectly to all individual as well as team task management needs. Key Features.

2019 111

2019 2006 2010 Software Review 111

Herding Cats

NOVEMBER 7, 2016

The same process for estimating is applied to multi-billion dollar projects we work. And the same process is applied to the Scrum development processes on those projects. . Here's some materials that provide the tools and processes needed to learn how to estimate. Springer International Publishing, 2016.

Estimate 64

Estimate 2006 2005 2013 64

ProProfs Project Management

JANUARY 15, 2021

Here’s how the project kanban board looks like: Kanban technique originated from Toyota’s “just-in-time” (JIT) production system and created by Taiichi Ohno who wanted a simple planning system in place to help them manage and control the production process efficiently. Coordinating Sales Process. However, after 1940 David J.

Software Review 81

Software Review Technical Review 2004 SCRUM 81

Herding Cats

MAY 7, 2019

So start here to build your academic foundation, that can be put to work to build a foundation of validated experience of making estimates in the presence of uncertainty and protect yourself from fallacious claims that estimates are a waste, not needed, and produce bad resulting in the decision making process for those paying you to produce value.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

MAY 10, 2019

IEEE Transactions on Software Engineering , Vol. Project Risk Management: A Combined Analytic Hierarchy Process and Decision Tree Approach,” Prasanta Kumar Dey, Cost Engineering , Vol. 255, April 2010. 24, 2010. “A Norton, The Systems Engineering Process Office, MITRE Corporation, 6 June 1999. 3, March 2002.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MARCH 11, 2017

This quote demonstrates a lack of understanding of making decisions in the presence of uncertainty and the processes and events that create uncertainty. There is naturally occurring variability from uncontrolled processes. Aleatory uncertainty is expressed as a process variability. First, let's establish a principle.

2003 46

2003 2014 2015 2011 46

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

Having a knowledge transfer process in place boosts the chance of project success by over 20%. [6]. Most Popular Agile Tools and Processes: Scrum – 43%. Lean & Test Driven Development (TDD) – 11%. Feature Development Driven – 9%. Dynamic Systems Development Method – 3%. Poor purchasing processes: 23%.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

Herding Cats

APRIL 4, 2019

Misconceptions of Risk , Terje Aven, John Wiley & Sons, 2010. Critical Code, Software Producibility for Defense, Committee for Advancing Software-Intensive Systems Producibility , Computer Science and Telecommunications Board Division on Engineering and Physical Sciences, National Research Council of the National Academies, 2010.

Risk Management 43

Risk Management Risk 2003 2011 43

Wrike

AUGUST 14, 2020

Toyota was looking for a way to improve their engineering and production processes. The Kanban process was the result of this adaptation. . Toyota used physical cards to signal separate steps in their manufacturing process. Anderson is often credited as being the first to implement Kanban in software development in 2005.

Software Review 36

Software Review Technical Review 2005 SCRUM 36

Herding Cats

DECEMBER 15, 2016

Laurens Eveleens and Chris Verhoef, IEEE Software , vol. 1, Jan-Feb 2010, pages 30-36. Forgetting even more that "agile" is a bottom-up software development solution. Chaos Report Myth Busters , . Willian pointed out the bands for measuring success. Related articles.

2006 28

2006 2010 Estimate Agile 28

Herding Cats

SEPTEMBER 19, 2018

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. This is a Closed Loop Control Systems for managing the performance of a Software Intensive System of Systems, all developed using Scrum.

Technical Review 43

Technical Review 2010 Estimate Software Review 43

EasyProjects

SEPTEMBER 24, 2019

Have you ever seen a chef send a dish out without tasting it several times at every stage of the process? According to the Project Management Institute, agile processes initially slow a team down because of the learning curve. There are three main agile methodologies to consider: Scrum, Kanban or Extreme Programming.

Agile 41

Agile Technical Review Software Review Underperforming Technical Team 41

Herding Cats

JANUARY 20, 2018

But in the software development world, the domains of IT, there are two other colors of money. There are two types of software that are developed for a business: 1) internal-use software, and 2) software developed to be sold, leased or marketed (“software to be sold”). CAPEX and OPEX.

Software 38

Software 2006 Software Developers Software Development 38

Herding Cats

APRIL 16, 2019

Management Processes (#MP). Agile Software Development (#ASD). While many of the presentations have similar titles, the content is focused on a specific set of processes and practices, while the principles are the same, since they are Immutable. . Management Processes. Project Performance Management (#PPM).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

MPUG

OCTOBER 9, 2019

But you’ve probably seen this in your career where you have people jumping around going, “Oh, hey, here’s the next silver bullet,” or, “We are going to turn into a scrum or an agile shop.” And so this is where agile kind of fits in and isn’t just necessarily only for software development.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

Workzone

APRIL 30, 2020

In 2010 daPulse, created by Wix.com , joined the vast array of project management tools on the market, and in 2017, daPulse went through a transformation to become Monday.com. Designed to come across as colorful and friendly, Monday aims to help you kick your case of the Monday blues through the use of its software.

2020 38

2020 Software Review Technical Review Software 38

MPUG

SEPTEMBER 9, 2020

Satya N Dash: In addition to that, I have seen management practitioners when they create a plan, they make a lot of mistakes, without any software tool, in this case Microsoft Project. As early as 2009, 2010, nearly 11 years before I was working as a PMO. Let us say there is a back-office on VPU processing.

Software Review 52

Software Review Critical Chain Technical Review Risk Management 52

Leading Agile

NOVEMBER 17, 2020

So we first worked together, I guess it was probably back in like late 2009, 2010. Talk to me about some of the challenges that you had taking it straight from a software development perspective. So— – We reconnected, yeah. I had joined Pillar for a little bit. – Right. – So it’s interesting.

Technical Review 112

Technical Review Software Review Agile Governance 112

MPUG

OCTOBER 16, 2019

There’s always a process. Remember if we talk about Scrum, we talk about chickens and pigs and the ability to, Hey look, you’ve got to listen on the sidelines, the team needs to come up with that and then they’ll engage you as they need to. Well, it’s important to have a good process. That is great.

Agile 40

Agile Technical Review Software Review Engineering 40