Herding Cats

JUNE 9, 2018

With these business principles of software development and projects in general, we can ask and answer five principles of project success. The success of a software product, service, and solution depends on good business, financial, and risk management. 5] "Decisions in software development projects management.

Transportation 39

Transportation Software Engineering Finance 2011 39

Herding Cats

MAY 10, 2019

IEEE Transactions on Software Engineering , Vol. 5, September/October 2011. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. Project Risk Management: Lessons Learned from Software Development Environment,” Y.

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

Techno-PM

MARCH 29, 2022

The British Standards Institution has accredited them to provide certification for ITIL® professionals based on their latest release, ITIL 2011. They know how to work with different teams, understand their needs, and bring together for successful project completion. Career paths after ITIL Certification: Learn More About the Course !

Certification 64

Certification 2011 Healthcare Retail 64

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 Are Problem Causes of Software Projects? All for the want of a nail.

2014 45

2014 Aerospace 2011 2013 45

Herding Cats

MARCH 11, 2017

“Quantifying Uncertainty in Early Lifecycle Cost Estimation (QUELCE),” Robert Ferguson, Dennis Goldenson, James McCurley, Robert Stoddard, David Zubrow, and Debra Anderson, Technical Report, CMU/SEI-2011-TR-026 ESC-TR-2011-026. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E.

2003 46

2003 2014 2015 2011 46

Herding Cats

JUNE 9, 2018

With these business principles of software development and projects in general, we can ask and answer five principles of project success. The success of a software product, service, and solution depends on good business, financial, and risk management. 5] "Decisions in software development projects management.

Transportation 28

Transportation Software Engineering Finance 2011 28

EasyProjects

SEPTEMBER 24, 2019

In the next section, we’ll explore how to take the next steps and put agile into action. How to be Agile. Let’s take a look at how you can apply agile methodologies at your workplace for better results. Pursuing continuous improvement and reflecting frequently on how to be more effective. Deliver code that is extensible.

Agile 41

Agile Technical Review Software Review Underperforming Technical Team 41

Digite

JANUARY 7, 2018

In this book, Mike takes a distinctive approach to the implementation of the Kanban Method and explains what it is, how its practitioners think, and to offer practical advice on how to apply it. hours, Published February 2nd, 2011 by Createspace Independent Publishing Platform). Personal Kanban: Mapping Work – Navigating Life.

Lean 79

Lean Software Review 2010 2014 79

Epicflow Blog

MAY 14, 2019

We’ve also received lots of great ideas on how to overcome the causes of project failure. Continue reading this part to find practical tips on how to mitigate these threats. David Lipper , a Knowledge Management UX Manager at Cenlar FSB, communicates a similar idea: “Learn how to build on momentum. Involve Your Stakeholders.

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75

Scrum.org

FEBRUARY 4, 2022

This post is a guide on how to bring a more evidence-based perspective to your claims. Where and how can you find evidence? How can you determine the quality of that evidence? Some of the references in the paper “The impact of inadequate customer collaboration on self-organizing teams” by Hoda, Noble & Marshall (2011).

Agile 183

Agile Software Review Underperforming Technical Team Technical Review 183

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? Scrum Values.

SCRUM 338

SCRUM Software Review Development Team Review Underperforming Technical Team 338

Stepping Into Project Management

MARCH 10, 2014

Today we interview Siddhartha Govindraj, who specializes in Lean/Agile processes for software development. He was nominated for the Brickell Key award in 2011, an award given by the Lean Software & Systems Consortium for recognizing achievements in the lean-agile industry and is also a Fellow of the Lean Systems Society.

2011 37

2011 Lean 2013 Agile 37

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

Wrike

SEPTEMBER 29, 2022

Wrike was launched in 2006 by founder and software developer Andrew Filev. The software makes it easy to customize your workspace to reflect your branding and tackle your needs. Rather than changing your processes to fit the software, you customize Wrike to fit your business. . What is Wrike? What is Asana? Customization.

2006 36

2006 2011 Software Budget 36

Scrum.org

JANUARY 15, 2022

But, the reality is that over the last 20+ years of the Agile Manifesto, the context, use, and experience with agile provides some evidence that there is a fundamental attribution error concerning the approach to Agile Software development and its execution. It can be a challenging leadership problem and problematic to resolve.

Agile 218

Agile 2001 2011 Software Developers 218

Herding Cats

MARCH 11, 2018

Take for example the deployment of an ERP system, the installation, and startup of a process control system, the release of a suite of embedded software controllers for a car, aircraft, petrochemical plant. A recent survey of 600 firms indicated that 35% of them had at least one "runaway' software project. Editors, Springer, 2011.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Herding Cats

OCTOBER 16, 2018

Those holding this view really say, we don't understand what models are for, how they're built, and how to apply them the model possible futures , without exploring outside of personal anecdotes. . Developing analytics models for software project management,” Morakot Choetkiertikul, University of Wollongong, September 9, 2018.

Aerospace 41

Aerospace Engineering 2012 2014 41

Scrum.org

APRIL 7, 2022

Bushe and Chu (2011) identify seven situations that drive the use of fluid teaming in those environments: High turnover among employees, leading to changes in teams. Through repetition, your body develops the reflexes to do this automatically — outside of your immediate awareness. It takes time to develop teams.

Underperforming Technical Team 157

Underperforming Technical Team 2007 2006 2009 157

Scrum.org

AUGUST 17, 2020

How to reduce this bias. Ross & Nisbett (2011) offer an extensive overview of research in this area. . How to reduce this bias. For example, the bias mostly disappears when people are made aware of how situational factors influence the behavior (e.g. How to reduce this bias. How to reduce this bias.

2015 214

2015 2014 2004 Influencer 214

Workzone

JULY 18, 2022

Proofhub is an all-in-one project planning software that was launched in 2011. Cons: It’s an enterprise-level tool that will take a while for your team to learn how to use it. If your team does software development or another DevOps field, Planio could be a great option. Project servers are quoted individually.

Software Review 26

Software Review Underperforming Technical Team 2022 Software 26

Agilemania

JANUARY 12, 2022

2011 marked a new beginning in the era of large-scale software project management. SAFe is a knowledge base of proven, integrated principles, practices, and competencies for attaining business agility using Lean, Agile, Systems Thinking, and DevOps to manage large scale software development. . But what is SAFe? .

Consulting 98

Consulting Certification Lean Underperforming Technical Team 98

Workzone

APRIL 23, 2020

Proofhub is an all-in-one project planning software that was launched in 2011. . Cons: It’s an enterprise-level tool that will take a while for your team to learn how to use it. If your team does software development or another DevOps field, Planio could be a great option. Project servers are quoted individually.

Software Review 26

Software Review Underperforming Technical Team Software Technical Review 26

Herding Cats

APRIL 16, 2019

Agile Software Development (#ASD). Here are presentations and paper on how to do that in a variety of domains. . Flawless Execution - Following the Afterburner them, here's how to flawlessly execute a project through the plan of the week. Enterprise IT and Embedded Systems (#EIT). Balanced Scorecard (#BSC).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

APRIL 4, 2019

Failure of Risk Management: Why It’s Broken and How to Fix It, Douglas Hubbard, 2009. Applied Software Risk Management: A Guide for Software Project Managers , C. Henry Montgomery (Editor), Universitetsforlaget; UK Edition, November 28, 2011. 3421, Second Edition, December 2011. Gideon Keren (Editor),?

Risk Management 43

Risk Management Risk 2003 2011 43

MPUG

MARCH 18, 2021

Jeff is currently the lead course developer for Edward’s Performance Solution and oversees the production and maintenance of courses on project management, systems engineering, software development, business process improvement, and cybersecurity. 2011, when we had that earthquake in Maryland. Just in, what?

Risk Management 52

Risk Management Software Review Underperforming Technical Team Governance 52

Digite

MARCH 12, 2018

These may seem like three distinct questions, but are, in my mind one: how to structure the Kanban board – around people, or around tasks? In my over 25+ years in the software industry, this has been an all too familiar situation! I have often wondered – doesn’t speak too well of us as software professionals!

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

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

Herding Cats

NOVEMBER 7, 2016

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. Numerical anchors and their strong effects on software development effort estimates,” Erik Løhrea, and Magne Jørgensen, Simula Research Laboratory, Oslo.

Estimate 64

Estimate 2006 2005 2013 64