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. Now To Risk Management.

Software Development 34

Software Development Software Developers Risk Management Risk 34

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.

2017 190

2017 2018 2016 SCRUM 190

Digite

MARCH 12, 2018

I have often wondered – doesn’t speak too well of us as software professionals! Far too many projects and teams are occupied by far too many crises all through the development/ implementation lifecycle. However, the fact is that software development is a complex activity – perhaps more so than any other type of projects?

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

Leading Agile

JANUARY 15, 2019

The title is based on a quote from the 2007 movie, Ghost Rider. Connection with Software Development. Software development teams often find themselves tangled up with more work than they can handle gracefully, if at all. The two fight briefly.

Software Review 90

Software Review Development Team Review 2007 Technical Review 90

Herding Cats

NOVEMBER 7, 2016

“Believing is Seeing: Confirmation Bias Studies in Software Engineering, “Magne Jørgensen and Efi Papatheocharous, 41st Euromicro Conference on Software Engineering and Advanced Applications (SEAA). The Use of Precision of Software Development Effort Estimates to Communicate Uncertainty,” Magne Jørgensen, Software Quality Days.

Estimate 64

Estimate 2005 2006 2012 64

Rebel’s Guide to PM

SEPTEMBER 26, 2016

She started her career as a software developer and is now an experienced consultant in organizational project management, especially dealing with IT organizations and software projects. She teaches project management at University of Padova and has been a PMI volunteer since 2007.

Software Review 150

Software Review Software Technical Review PMI 150

Scrum.org

AUGUST 17, 2020

People often fail to understand this fallacy because they underestimate how much of their behavior and their outcomes are influenced by randomness (Taleb, 2007). The Dunning-Kruger effect manifests when people without any experience with software development make strong claims about how easy a particular change should be.

2015 230

2015 2014 2004 Influencer 230

The IIL Blog

JANUARY 24, 2024

Most of these roles were based on aspects of IT operation, such as mainframe operation and maintenance, which later evolved into software development and commercialisation. ITIL v2 followed this in 2001, ITIL v3 in 2007, and ITIL 4 in 2019. As ITSM evolved, so did the ways of delivering Information Technology services.

2001 78

2001 2007 Information Technology 2005 78

Leading Agile

JUNE 27, 2018

The impression was reinforced strongly when I attempted to bridge the divide by participating in the academic tracks of agile and technical conferences in the 2007-2008 time frame. They weren’t professional software developers, and they were pretty new at the whole process of doing research, as well.

Software Review 121

Software Review Technical Review Underperforming Technical Team 2007 121

International Institute for Learning

JUNE 2, 2022

Rubin Jen has been in the project management field for over 23 years, spanning aerospace, engineering, telecom, software development, outsourcing, consulting, not-for-profit and government sectors. I’m one of the few trainers who got the CSM certification early on [2007]. Roy may be the only other one.

Agile 59

Agile Aerospace 2007 Telecoms 59

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 ? 37–48, 2007. Steve McConnell. Quantifying IT Forecast Quality,” J. Eveleens and C.

2012 48

2012 2007 2011 2010 48

Online PM Courses

OCTOBER 14, 2018

Serving the project management community since 2007 with fresh project management articles every day! Agile Alliance is a nonprofit organization dedicated to promoting the concepts of Agile software development as outlined in the Agile Manifesto. Software development for 40 years. PM Blogs and Bloggers.

PMO 96

PMO Underperforming Technical Team PMI Technical Review 96

Productivity Land

SEPTEMBER 11, 2023

Technology was used for several years in classrooms around the globe just like a supplement or alternative route of learning and teaching; however, today’s e-books are better than previously (e-readers were first introduced in 2007). Educational software is more effective than traditional methods for many reasons.

Software Review 77

Software Review Software Technical Review 2007 77

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! And since 2007, that community has included the Planio team! What is Redmine? Reliability.

2006 88

2006 2007 Closing Agile 88

Herding Cats

MAY 7, 2019

Effort Distribution to Estimate Cost in Small to Medium Software Development Project with Use Case Points,” Putu Linda Primandari and Sholiq, The Third Information Systems International Conference, Procedia Computer Science, 72, pp. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

JULY 24, 2017

It's suggested from observations, the Cone of Uncertainty (CoU) is not a valid model of how uncertainty behaves in software development projects. In all software development businesses, showing up late and over budget has a direct impact on the bottom line. . 37–48, 2007. . Laird and M. Related articles.

2007 42

2007 2012 2006 2008 42

Project Pulse Journal

APRIL 15, 2024

Ready to transform your approach to project management and software development? Exploring Agile methodologies provides teams with flexible, efficient, and collaborative approaches to software development and project management. Columns include "Reported," "Confirmed," "In Development," "Testing," and "Deployed."

Software Review 52

Software Review Technical Review Agile SCRUM 52

Herding Cats

MAY 10, 2019

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. Recent trends of Risk Management in Software Development: An Analysis,” Raghavi Bhujang and V.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Agilemania

FEBRUARY 23, 2023

Concerns were voiced in the IT operations and software development sectors from 2007 to 2008 about the old software development paradigm that split operations from developers regarding how code was distributed and supported. DevOps was formed by combining the concepts of development and operations.

Software Review 52

Software Review Technical Review Certification 2007 52

Herding Cats

OCTOBER 30, 2018

This document is all but unknown in the Enterprise IT domain and completely unknown in the agile software development world. This missing document is a root cause of many failures in tradition and agile software development. Thesis, School of Aerospace Engineering, Georgia Institute of Technology, May 2007.

Planning 109

Planning 2007 Technical Review 2009 109

Herding Cats

DECEMBER 3, 2017

Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. Coping with the Cone of Uncertainty: An Empirical Study of the SAIV Process Model," Da Yang, Barry Boehm, Ye Yang, Qing Wang, and Mingshu Li, ICSP 2007, LNCS 4470, pp. 37-48, 2007.

2007 34

2007 2012 2009 2010 34

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. 255, April 2010. 920, November 2004. Kwak and J.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Epicflow Blog

JANUARY 12, 2021

As, for example, an IT project manager orchestrates IT projects and leads corresponding teams in their software development efforts. Paper presented at PMI® Global Congress 2007—North America, Atlanta, GA. You can guess their main focus of work by their titles. The industry a PM works in defines the specifics of projects. .

PMO 62

PMO 2007 Controlling 2027 62

Herding Cats

MARCH 11, 2017

Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp. Architecting Large Scale Agile Software Development: A Risk–Driven Approach,” Ipek Ozkaya, Michael Gagliardi, Robert L. 12, 2008. “A

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. Gano, Atlas Books, 2007. A Correction fixed the immediate non-conformance.

2014 45

2014 2011 Aerospace 2013 45

Herding Cats

APRIL 4, 2019

Software Risk Management , Barry W. Strategic Risk Taking: A Framework for Risk Management , FT Press, August 12, 2007. Applied Software Risk Management: A Guide for Software Project Managers , C. Ravindranath Pandian, Auerbach Publications, 2007. Stewart, ACTEX Publications, 2006.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

NOVEMBER 5, 2018

In software development, those managing the project have some understanding the market forces (from their marketing departments), the technology (from their engineering department), and how to manage in the presence of Aleatory and Epistemic risk (the managers running a successful firm). Software development is a non-ergodic process.

Software Review 34

Software Review Estimate Technical Review Software Development 34

Herding Cats

AUGUST 1, 2018

“The Cone of Uncertainty,” Stephen Gryphon, Phillippe Kruchten, and Steve McConnell, Letters, IEEE Software , 23 (5) 2006, pp 8?10. Coping with the Cone of Uncertainty: An Empirical Study of the SAIV Process Model,” Da Yang, Barry Boehm, Ye Yang, Qing Wang, and Mingshu Li, ICSP 2007 , LNCS 4470, pp. 37–48, 2007.

2012 29

2012 2007 2010 2006 29

Wrike

SEPTEMBER 2, 2009

The idea of constant dialogue in project management surfaced in 2001 as one of the principles of so-called agile software development and is described in the Agile Manifesto. Now agile methods are used to manage various projects outside of the software development. Agile Management Essentials.

Agile 42

Agile 2006 2003 2001 42

Planio

JULY 22, 2020

If you’re also interested in Agile project management, pair the PMBOK with the PMI’s new Agile Practice Guide or our own Guide on How to Pick the Software Development Process that’s Right For you. Published date: 2007. Project Management for Humans: Helping People Get Things Done. Author: Brett Harned. Published date: 2017.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

Herding Cats

APRIL 16, 2019

Agile Software Development (#ASD). Those lessons are directly transferable to the management of software development teams. Parametric Project Monitoring and Control - Earned Value is an approach to Performance measurement for monitoring and controlling the progress of software development projects.

Technical Review 42

Technical Review Performance Measurement 2003 Governance 42

Herding Cats

JULY 7, 2018

In project management and especially the software development project management domain, making decisions is always about making decisions in the presence of uncertainty. Uncertainty is always in place for the cost, schedule, and the technical attributes of any software project.

2007 30

2007 Estimate Software Development Software Developers 30

Wrike

APRIL 12, 2016

In his conversational writing style, he tackles the parallels between software development and marketing, walks you through the workflows and best practices behind Agile marketing, and lays out everyday tactics for managing the entire marketing process successfully.

2014 36

2014 2015 2016 Technical Review 36

Herding Cats

JULY 7, 2018

In project management and especially the software development project management domain, making decisions is always about making decisions in the presence of uncertainty. Uncertainty is always in place for the cost, schedule, and the technical attributes of any software project.

2007 28

2007 Estimate Software Development Software Developers 28

Herding Cats

JANUARY 22, 2017

Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Development Effort Estimation: Formal Models or Expert Judgment?” IEEE Software, March-April 2009, pp. A Systematic Review of Software Development Cost Estimation Studies,” IEEE Trans. Software Eng.,

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Development Effort Estimation: Formal Models or Expert Judgment?” IEEE Software, March-April 2009, pp. A Systematic Review of Software Development Cost Estimation Studies,” IEEE Trans. Software Eng.,

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Development Effort Estimation: Formal Models or Expert Judgment?” IEEE Software, March-April 2009, pp. A Systematic Review of Software Development Cost Estimation Studies,” IEEE Trans. Software Eng.,

Technical Review 28

Technical Review Estimate 2005 Software Review 28