Scrum.org

FEBRUARY 4, 2022

There are dozens of high-quality academic works to draw from, there are dozens of academic journals dedicated to (agile) software development (ASD) and change management. Some of the references in the paper “The impact of inadequate customer collaboration on self-organizing teams” by Hoda, Noble & Marshall (2011). That is great!

Agile 193

Agile Software Review Underperforming Technical Team Technical Review 193

MPUG

SEPTEMBER 28, 2020

The following are examples of factors from the PMBOK Guide that lead to said project’s creation: Business process improvements. Software development. Even if you do not have defined model in place, you probably have some processes that could be used as part of your selected methodology. Competitive forces. New Technology.

Retail 119

Retail PMI 2001 2011 119

Agilemania

JANUARY 24, 2022

The entire organization had to be in the process, not just a few self-managed teams. . In 2011, Dean Leffingwell codified SAFe, the Scaled Agile Framework , to help bring the success that small teams have enjoyed with various agile methodologies such as Scrum or XP but scaled to the enterprise. Continuous Learning Culture.

Agile 98

Agile Lean 2011 SCRUM 98

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 ? The program management processes should seek to reduce uncertainty in the variable of the project. 1, January 2011. "A

2012 48

2012 2007 2011 2010 48

Herding Cats

MAY 7, 2019

So start here to build your academic foundation, that can be put to work to build a foundation of validated experience of making estimates in the presence of uncertainty and protect yourself from fallacious claims that estimates are a waste, not needed, and produce bad resulting in the decision making process for those paying you to produce value.

Estimate 40

Estimate Software Review Software 2012 40

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”. hours, Published February 2nd, 2011 by Createspace Independent Publishing Platform). Personal Kanban: Mapping Work – Navigating Life. By Jim Benson.

Lean 79

Lean Software Review 2010 2014 79

Herding Cats

MAY 10, 2019

IEEE Transactions on Software Engineering , Vol. 5, September/October 2011. Project Risk Management: A Combined Analytic Hierarchy Process and Decision Tree Approach,” Prasanta Kumar Dey, Cost Engineering , Vol. Norton, The Systems Engineering Process Office, MITRE Corporation, 6 June 1999. 3, March 2002. 255, April 2010.

Risk Management 38

Risk Management Risk Technical Review 2002 38

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

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

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. Business, Technical, Systems, Risk, and Project Management Briefings and Presentations.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Digite

MARCH 12, 2018

In the usual Scrum process, the P.O. 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. Also, we have quite diverse roles in the team (i.e.,

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

International Institute for Learning

SEPTEMBER 20, 2022

The idea is that for the most critical issues the leader should be always present. Visionary impulse is not needed, and therefore it is better to involve, as much as possible, all the team members in the decisions making process., Beedle, “Agile Software Development with Scrum”, Upper Saddle River, NJ, Prentice-Hall, 2002.

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52

Herding Cats

OCTOBER 20, 2017

For software development systems like Kanban, which is production line-centric, Litle's Law tells us. λ = average production rate of complete software components. λ = average production rate of complete software components. There are two fundamental assumptions for Little's Law to work in the software development domain".

Underperforming Technical Team 34

Underperforming Technical Team 2008 Software Developers Software Development 34

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

MPUG

MARCH 18, 2021

And like all MPUG presentations, a recording will be posted to mpug.com shortly after the live session ends. If you have any questions during today’s presentation, please send those over at any time using the chat question box on the go to webinar control panel. You can do that by logging into mpug.com. So this go around, right?

Risk Management 52

Risk Management Software Review Underperforming Technical Team Governance 52

Workzone

AUGUST 4, 2021

No other software on the market offers such an extensive onboarding and training process included with their subscription. It’s easy for our group to manage and our users to submit and follow along as to where a project is during the process. Each project is presented as a “board,” and broken up into “lists” and “cards.”

2021 26

2021 Software Review Technical Review Underperforming Technical Team 26