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. I will explain the peer review at the end of this article.

2017 172

2017 2018 2016 SCRUM 172

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. Market testing: Next, your product will be launched in a controlled market environment so that potential customers can review it and offer feedback. Start your free trial of Wrike today.

Innovation 36

Innovation Process Technical Review Artificial Inteligence 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. 37–48, 2007. .

2007 42

2007 2012 2006 2008 42

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 72

PMO Technical Review Underperforming Technical Team PMI 72

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”. This is due to many reasons. We have a target weight at Test Readiness Review of 23KG. Software Engineering Economics”. Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10] 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”. This is due to many reasons. We have a target weight at Test Readiness Review of 23KG. Software Engineering Economics”. Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10] 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”. This is due to many reasons. We have a target weight at Test Readiness Review of 23KG. Software Engineering Economics”. Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10] Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen,

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Leading Agile

JUNE 27, 2018

In 2012, I wrote a blog post entitled “Delivering provably-correct code.” ” In it, I suggested several approaches developers could use to gain high confidence that their code would be suitable for release. When I took an interest in this loop, I quickly ran afoul of academics. Steadfastly Missing the Point.

Software Review 91

Software Review Technical Review Underperforming Technical Team 2007 91

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.

2002 192

2002 SCRUM 2007 2003 192

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

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. However, several studies show that cohesion positively impacts performance only in later stages of team development (e.g. Bradley et. Or if these processes can be fast-tracked.

Underperforming Technical Team 157

Underperforming Technical Team 2007 2006 2009 157

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

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. cutting corners only results in the illusion of speed.

Software Review 71

Software Review Development Team Review 2007 Technical Review 71

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

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 214

2015 2014 2004 Influencer 214

Planio

JULY 22, 2020

The Culture Code: The Secrets of Highly Successful Groups. 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. Author: Harvard Business Review. Author: Brett Harned.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

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

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

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

MPUG

OCTOBER 9, 2019

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. Today’s session is eligible for one PMI PDU in the technical category and the code for claiming today’s session is on the screen now.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

MPUG

NOVEMBER 14, 2019

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. And you get asked a question to enter a code. And this code is 18 11 17. And during the 2007 and 2003 versions, we got a new way of creating reports.

2013 40

2013 Finance 2007 Software Review 40

Herding Cats

NOVEMBER 7, 2016

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 ‒ Steve McConnell. The Future of Systems-and Software Development. Springer International Publishing, 2016.

Estimate 64

Estimate 2006 2005 2013 64

MPUG

DECEMBER 4, 2019

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. Everybody keep in mind that Microsoft Project is not accounting software; it is a project management tool. All right, commercial’s over. Kyle: All right.

Software Review 52

Software Review Initiating Software Closing 52

MPUG

OCTOBER 24, 2019

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. We’re going to take a quick review of Agile options and approaches. I can actually color code these. You can always come and change a due date.

Agile 40

Agile Technical Review Software Review Underperforming Technical Team 40