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. México, 1 al 3 de Febrero de 2006. De Meyer, C.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Planio

JULY 9, 2020

If you’re looking for a new project management tool, this guide will run you through the basics of what Redmine is, why it’s a great choice for most software development teams, and how you can get it set up and optimized for you! Redmine was launched in 2006 and is still being regularly updated. What is Redmine? Need convincing?

2006 88

2006 2007 Closing Agile 88

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. While Scrum is probably most prevalent in IT, Kanban and Lean are significant too. The method wars.

Agile 94

Agile Lean 2005 Risk Management 94

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

DECEMBER 15, 2016

The Standish report: does it really describe a software crisis?" 8, pages 15-16, August 2006. Laurens Eveleens and Chris Verhoef, IEEE Software , vol. Forgetting even more that "agile" is a bottom-up software development solution. The Bunk of Using decades-old report (1966) for basis of #NoEstimates conjectures.

2006 28

2006 2010 Estimate Agile 28

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? For instance, in 2006, Salesforce.com went all-out with change across the whole organization from the start and successfully completed a transformation from traditional management to Agile management in just three months.

Agile 41

Agile Technical Review Software Review Underperforming Technical Team 41

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

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. This post is my attempt to do this. Bradley et.

Underperforming Technical Team 166

Underperforming Technical Team 2007 2006 2009 166

Scrum.org

AUGUST 17, 2020

See how approaches like the Scrum Framework and Liberating Structures can prevent some of these biases by bringing in diverse voices and by validating your assumptions against reality. For me personally, it's one of the reasons why I like the Scrum Framework , as it gives guide-rails to help us think and validate our assumptions with data.

2015 220

2015 2014 2004 Influencer 220

Planio

JULY 22, 2020

Scrum: The Art of Doing Twice the Work in Half the Time. Project management is as much about people as it is about processes. Why you should read this: Once you master the materials inside the PMBOK you’ll have a process for initiating and successfully running any project. Scrum: The Art of Doing Twice the Work in Half the Time.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

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

APRIL 4, 2019

Stewart, ACTEX Publications, 2006. Software Risk Management , Barry W. Agile Risk Management and Scrum , Alan Moran, Institute for Agile Risk Management, 2014. Loch, Arnoud DeMeyer, and Michael Pich, Wiley, 2006. Software Engineering Risk Management , Dale Karolak, IEEE Computer Society Press, 1996.

Risk Management 43

Risk Management Risk 2003 2011 43

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

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. For software development starts with. DON'T DO STUPID THINGS ON PURPOSE (DDSTOP).

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. Analytical Hierarchical Process . Some Model-Based Systems Engineering process.

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. Does that make sense to anyone who has worked in software development? Probably not. .

Estimate 35

Estimate Underperforming Technical Team Technical Review Software Review 35

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

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

BeeWits

JULY 3, 2018

As a company, Wrike is the provider of a cloud-based project management and collaboration software, based in Silicon Valley, the San Francisco Bay Area. As you may know, the API can be used to perform custom development to connect your own business applications and processes to the service, essentially creating your own custom integration.

Software Review 29

Software Review Underperforming Technical Team Budget Defining 29

Wrike

MARCH 14, 2023

Due to its origins in software engineering, Jira is great for issue management. Agile teams respond well to Jira because it was built to make scrums, sprints, and Kanban methodology easy with boards, backlogs, and roadmaps. It has a robust ticketing system that can help track and resolve problems in an efficient way. What is Wrike?

Software Review 41

Software Review Technical Review 2006 Engineering 41