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

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

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 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

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. Software Engineering Institute, January 1996. México, 1 al 3 de Febrero de 2006.

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

Planio

JULY 9, 2020

Even software. Comfort knowing you’re always running the latest, most stable version of the software. 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!

2006 88

2006 2007 Closing Agile 88

Wrike

JANUARY 12, 2024

Jeff Kinney’s hit children’s book series, Diary of a Wimpy Kid , was first released in 2007 and is still rolling out installments each year. Adopt Agile methodologies Agile methodologies, widely used in software development, can be applied to the NPD process to shorten development cycles and boost team collaboration.

Innovation 36

Innovation Process Technical Review Artificial Inteligence 36

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. And if the competitor is shipping software with greater value, how does the Cone impact that? 37-48, 2007. 37-48, 2007.

2007 34

2007 2012 2009 2010 34

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

2007 42

2007 2012 2006 2008 42

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

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 174

2017 2018 2016 SCRUM 174

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 Developers Software Development 30

Online PM Courses

OCTOBER 14, 2018

Software Vendors. Serving the project management community since 2007 with fresh project management articles every day! Dedicated to provide PM articles, detailed PM software reviews, PM book reviews, and the latest news for the most popular web-based collaboration tools: Project-Management.com. Software Vendors.

PMO 73

PMO Technical Review Underperforming Technical Team PMI 73

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 Developers Software Development 28

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. What factors lead to software project failure?”

2014 45

2014 Aerospace 2011 2013 45

Herding Cats

MARCH 11, 2017

The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. Nord, CrossTalk: The Journal of Defense Software Engineering , May/June 2013.

2003 46

2003 2014 2015 2011 46

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

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. Software Engineering Economics”. Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10] Controlling Software Projects: Management, Measurement, and Estimation, Yourdon Press, 1982. [13] Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen,

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. Software Engineering Economics”. Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10] Controlling Software Projects: Management, Measurement, and Estimation, Yourdon Press, 1982. [13] Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen,

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. Software Engineering Economics”. Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10] Controlling Software Projects: Management, Measurement, and Estimation, Yourdon Press, 1982. [13] Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen,

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

MARCH 4, 2017

Let's start with a clear and concise description of the problem of successfully managing projects in the presence of uncertainty: Accurate software cost and schedule estimations are essential for non-trivial software projects. As a software project progresses, more information about the project is known. 37–48, 2007.

2010 28

2010 2007 Estimate Aerospace 28

Scrum.org

FEBRUARY 3, 2020

A while ago, I received an interesting scientific article from Gunther Verheyen titled “Getting Things Done: The Science Behind Stress-Free Productivity” (Heylighen & Vidal, 2007). Software development is (generally speaking) very complex. Why our brain is not built for software engineering. Open Source Jahrbuch (2007).

2002 203

2002 SCRUM 2007 2003 203

Rebel’s Guide to PM

SEPTEMBER 26, 2016

The project and portfolio management (PPM) software market is changing. In this article we look at emerging software in the PPM space and discuss how its selection and implementation needs to be done in line with an overarching digital strategy. A tiny snapshot of the analysis that the different software tools went through.

Software Review 150

Software Review Software Technical Review PMI 150

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. Service Integration and Management, aka SIAM, was developed in 2005.

2001 78

2001 2007 2024 Information Technology 78

Scrum.org

APRIL 7, 2022

Wang et al (2006) studied software teams tasked with ERP implementations and found that cohesive teams performed significantly better than less-cohesive teams. Teams generally develop through a number of stages, although scientific models vary in which stages and in what order. Information and Software Technology , 48 (4), 235–244.

Underperforming Technical Team 169

Underperforming Technical Team 2007 2006 2009 169

Herding Cats

JUNE 19, 2017

The Cone of Uncertainty is a framing assumption used to model the needed reduction in some parameter of interest in domains ranging from software development to hurricane forecasting. Shrinking The Cone Of Uncertainty With Continuous Assessment For Software Team Dynamics In Design And Development,” Pongtip Aroonvatanaporn,” Ph.D.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

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. Change in Communication.

Agile 42

Agile 2006 2003 2001 42

Leading Agile

JUNE 27, 2018

When they talk about the “correctness” of software, they’re talking about two different things. When a customer asks me to write a service, they aren’t asking for a mathematical model; they’re asking for working software. They didn’t rely on a study to teach them how to build software.

Software Review 123

Software Review Technical Review Underperforming Technical Team 2007 123

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 89

Software Review Development Team Review 2007 Technical Review 89

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 82

PMO 2007 Controlling Construction 82

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 222

2015 2014 2004 Influencer 222

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

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

Digite

MARCH 12, 2018

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! Far too many projects and teams are occupied by far too many crises all through the development/ implementation lifecycle.

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

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. Agile Software Development (#ASD). Enterprise IT and Embedded Systems (#EIT).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

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 projects are non-ergodic.

Software Review 34

Software Review Technical Review Estimate Software Developers 34