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). Scrumban and Other Essays on Kanban Systems for Lean Software Dev.

Lean 79

Lean Software Review 2010 2014 79

Gunther Verheyen

APRIL 24, 2020

Having worked with Scrum since 2003, I am fascinated by its ever-expanding use, which is not limited to software and (new) product development. Jeff Sutherland and Ken Schwaber moved the development of Scrum forward in the early 1990s. Ken Schwaber first documented Scrum in 1995 in the paper “ SCRUM Development Process.”

SCRUM 110

SCRUM 2003 2010 2013 110

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

MARCH 17, 2019

Here are my collected works, presentations, briefings, journal papers, articles, white papers, and essays, used to increase the Probability of Project Success (PoPS) I've developed and applied over my career in the software-intensive system of systems domain. Managment Processes. Presentations and Briefings. Flawless Execution.

2003 54

2003 2011 2008 Performance Measurement 54

Herding Cats

OCTOBER 5, 2018

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 ? This variation can be explained by the fact that initial concepts do not describe the final software system accurate enough.

2012 48

2012 2007 2011 2010 48

Scrum.org

MAY 26, 2020

“ Christiaan : A friend of mine started a software company. He sold solutions, I developed them. Barry : Failed software development projects. Barry : Failed software development projects. In 2010 I worked as a project manager for a web agency. Developers, because of the growing crunch-culture.

Agile 99

Agile 2004 SCRUM Software Developers 99

Herding Cats

MAY 10, 2019

This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. IEEE Transactions on Software Engineering , Vol. 255, April 2010. 24, 2010. “A México, 1 al 3 de Febrero de 2006. 3, March 2002.

Risk Management 38

Risk Management Risk Technical Review 2002 38

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

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

JUNE 5, 2019

Why is there such a strong emphasis on the people needed for the process and so little on the people doing the work? Agile software development started with developers. These days, it seems to be more about Scrum Masters, Agile Coaches, Product Owners, and other “process roles”. But I doubt the reverse is true.

SCRUM 139

SCRUM 2002 2003 2001 139

Project Pulse Journal

MARCH 25, 2024

The development process of products and the project lifecycle integrate to deliver the perceived value to stakeholders. Product Life Cycle Management Managing the life cycle of products from planning and development to launch and sustainment is vital for adapting to evolving customer expectations and technological advancements.

Sustainability 52

Sustainability Innovation Development Team Review 2024 52

Herding Cats

AUGUST 1, 2018

Specific actions to reduce the Episuncertaintiesnaties and Margin to handle the Aleatory uncertainies are part of any good project management process. . The Cone of Uncertainty,” Stephen Gryphon, Phillippe Kruchten, and Steve McConnell, Letters, IEEE Software , 23 (5) 2006, pp 8?10. 37–48, 2007.

2012 29

2012 2007 2010 2006 29

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

Wrike

MAY 23, 2023

I joined the team as a QAA engineer in 2010, the first employee in this role. 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. Hello, everyone! I’m Alexander, and I’m a QAA manager at Wrike.

Engineering 36

Engineering Underperforming Technical Team Controlling Software Review 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 333

SCRUM Software Review Development Team Review Underperforming Technical Team 333

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. 37-48, 2007. 37-48, 2007.

2007 34

2007 2012 2009 2010 34

Herding Cats

NOVEMBER 14, 2018

When we hear of the difficulties of making decisions in the presence of uncertainty, especially about software features and capabilities, there are straightforward ways to solve this problem. This method is the Analytic Hierarchy Process (AHP). AHP was developed in the 1970s by Dr. Thomas Saaty. The Wrap Up .

Technical Review 47

Technical Review 2010 2014 Software Developers 47

Herding Cats

JANUARY 9, 2017

Aleatory uncertainty, which is the naturally occurring yields variances in the underlying processes. Epistemic uncertainty comes from probabilistic processes that can be addressed with handling responses. The idea of risk and its management and handling is a critical success factor for all software development.

Estimate 28

Estimate Risk 2010 Software Engineering 28

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

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. Wallshein, Ph.D. Laird and M.

2007 42

2007 2012 2006 2008 42

Herding Cats

DECEMBER 15, 2016

The Non-Existent Software Crisis: Debunking the Standish Report. The Standish report: does it really describe a software crisis?" 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.

2006 28

2006 2010 Estimate Agile 28

Herding Cats

APRIL 8, 2017

Much of the conversation in social media around agile techniques seems to be based on the differences between the variety of choices of a method, a process, or a practice and definitions of terms for those choices. These systems fall into the Software Intensive System of Systems (SISoS) category.

Web Development 37

Web Development Software Engineering Engineering 2010 37

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? Agile is most popular in the software industry, but it has found homes in the information technology, engineering, product development, and marketing industries to name a few. Disgusting. Well, you kinda deserved that.

Agile 41

Agile Technical Review Software Review Underperforming Technical Team 41

Herding Cats

MARCH 4, 2017

The uncertainty is always there, it doesn't go away with specific actions in specific domains, or with the use of any tools, processes, or practices. As a software project progresses, more information about the project is known. Many of the programs we work are Software Intensive System of Systems.

2010 28

2010 2007 Estimate Aerospace 28

Leading Agile

NOVEMBER 17, 2020

And in that we grew the company where originally, we did a mixture, as you know, between transformation and building custom software solutions. Over time, we grew to focus more, mainly on customer soft, custom software solutions, and eventually Accenture purchased us. So— – We reconnected, yeah. – Interesting.

Technical Review 112

Technical Review Software Review Agile Governance 112

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

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

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. The Measure that is modeled in the Cone the variable is the Quantitative basis of a control process that establishes the goal for the performance measure. The processes is an engineering discipline. The notion of the Cone of Uncertainty has been around for awhile.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. The Measure that is modeled in the Cone the variable is the Quantitative basis of a control process that establishes the goal for the performance measure. The processes is an engineering discipline. The notion of the Cone of Uncertainty has been around for awhile.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Project Management Hacks

AUGUST 4, 2016

Through many discussions with my husband – who works in software development – I discovered an interest in the technology field. I led an effort to develop a risk-based software development process. We developed the process with input from the user community, including business partners as well.

2013 28

2013 2003 Technical Review 2010 28

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. The Measures that are modeled in the Cone of Uncertainty are the Quantitative basis of a control process that establishes the goal for the performance measures. The processes is an engineering discipline. The notion of the Cone of Uncertainty has been around for awhile.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Scrum.org

APRIL 7, 2022

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. Even a single change in team membership can disrupt that process, and consequently, make it harder for teams to become high-performing sooner.

Underperforming Technical Team 165

Underperforming Technical Team 2007 2006 2009 165

MPUG

JANUARY 4, 2021

For at least twenty years and counting, the world around us has become more and more software driven, and, as a result, more digital. Electric vehicles are about 50% software, in terms of value, whereas fossil fuel cars are mostly hardware. Banks have essentially been software developing organizations for a long time.

Artificial Inteligence 122

Artificial Inteligence Critical Chain Underperforming Technical Team Agile 122

nTask

AUGUST 8, 2019

This helped us to simplify how nTask project management software can be used for solving such issues. We have gone an extra mile to illustrate various real life use cases and examples where waterfall is implemented, and how one can use nTask to further simplify that process – so on and so forth. On 29 June 1956, Herbert D.

Software Review 97

Software Review 2019 Development Team Review Technical Review 97

Herding Cats

APRIL 4, 2019

Research shows that for projects, especially software projects Aleatory uncertainty is the predominant source of risk. So here are some books, handbooks, and guides that sit on my shelf that are used pretty much all the time on the Software Intensive System of Systems we work on. Software Risk Management , Barry W.

Risk Management 43

Risk Management Risk 2003 2011 43

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. Management Processes (#MP). Agile Software Development (#ASD).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Wrike

NOVEMBER 7, 2018

Project Management Software & Tools. 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%.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60