Scrum.org

FEBRUARY 25, 2021

In the previous article, Agile Transformation – Success Factors part 1 , there was a strong focus on key levels that should be taken first into consideration. Top-management is actively involved in the process, decisions are being made according to evidence. This process requires self-awareness, maturity and transparency. .

Agile 137

Agile Lean 2011 2015 137

Scrum.org

FEBRUARY 22, 2021

Scrum has proven to be an effective product delivery framework for all sorts of products. However, Scrum is equally well suited to build the wrong product efficiently as its Achilles heel has always been the product discovery part. How that is supposed to happen is nowhere described in the Scrum Guide. Think of “MVP.”).

Software Review 149

Software Review Technical Review Cadence SCRUM 149

Scrum.org

APRIL 16, 2019

The comparison between Kanban and Scrum obviously comes up often when we're talking to teams, especially in the context of Professional Scrum with Kanban. Scrum is quite clear about the topic (Quoting the Scrum Guide ). Scrum Teams are self-organizing and cross-functional. To Team or not to Team? Mixing it up.

Initiating 127

Initiating 2011 Software Review SCRUM 127

MPUG

SEPTEMBER 28, 2020

The following are examples of factors from the PMBOK Guide that lead to said project’s creation: Business process improvements. 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. Contains consistent and repeatable processes. Customer request.

Retail 119

Retail PMI 2001 2011 119

International Institute for Learning

MAY 16, 2022

One of my favorite articles is from Bernard Marr, a leader in the 4IR discussion: What Is The 4th Industrial Revolution, And What Does It Mean For You? Another article written more from an Agile Practitioner’s perspective is RGP’s How Business Agility Helps You Thrive in the Age of Disruption. Under Tim Cook, Apple Inc.

Artificial Inteligence 59

Artificial Inteligence Agile Cadence 2011 59

Herding Cats

DECEMBER 16, 2017

Estimating Software-Intensive Systems: Projects, Products, and Processes , Richard Stutzke, Addison-Wesley, 2005. Practices for Scaling Lean & Agile Development: Large, Multisite, and Offshore Product Development with Large-Scale Scrum , Craig Larman and Bas Vodde, Addison Wesley, 2010. Related articles. Prentice Hall, 2000.

Software Developers 46

Software Developers Software Development Estimate 2006 46

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 10, 2019

5, September/October 2011. Project Risk Management: A Combined Analytic Hierarchy Process and Decision Tree Approach,” Prasanta Kumar Dey, Cost Engineering , Vol. A Simulation-Based Risk Network Model for Decision Support in Project Risk Management,” Chao Fang and Franck Marle, in Decision Support Systems , Elsevier, 2011.

Risk Management 38

Risk Management Risk Technical Review 2002 38

ProjectManager.com

AUGUST 29, 2023

Plus we’ve added handy links to help you dive deeper into different topics with videos, articles and even our round-up of all resources so you can put these important terms into practice with your projects. Read Peter Landau’s article How to Write a Business Case to learn more about its structure.

Software Review 393

Software Review Underperforming Technical Team Lean Event Chain 393

Herding Cats

MAY 11, 2019

5, September/October 2011. Project Risk Management: A Combined Analytic Hierarchy Process and Decision Tree Approach,” Prasanta Kumar Dey, Cost Engineering , Vol. A Simulation-Based Risk Network Model for Decision Support in Project Risk Management,” Chao Fang and Franck Marle, in Decision Support Systems , Elsevier, 2011.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Scrum.org

FEBRUARY 4, 2022

What contexts are Scrum suited to, and which not? What if you end up applying a methodology like Scrum to a context where it isn’t suited, and people leave the company as a result? when everyone is pro-Scrum, or against SAFe or against estimation, or exclusively Scrum Masters? Is scaling always a bad idea?

Agile 204

Agile Software Review Underperforming Technical Team Technical Review 204

Herding Cats

JANUARY 20, 2018

Let's start with that dreaded waterfall development process. In the waterfall accounting process there are three phases in software development: Preliminary project stage or evaluation phase , which establishes the technical feasibility of the project. So Now What About Agile Development Processes. What drives such decisions?

Software 38

Software 2006 Software Developers Software Development 38

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. We want to describe the context of SIPOC within business process creation and improvement.

Risk Management 52

Risk Management Software Review Underperforming Technical Team Governance 52

The IIL Blog

JUNE 28, 2018

Innovation management , in its purest form, is a combination of the management of innovation processes and change management. It refers to products, services, business processes, and accompanying transformational needs, whereby the organization must change the way they conduct their business. The change can be incremental or radical.

Innovation 106

Innovation 2008 2011 2010 106

Workzone

JULY 18, 2022

Organization – Project management software organizes process, projects, and documents by keeping everyone on the same page on what needs to be tracked, how and where. No other software on the market offers such an extensive onboarding and training process included with their subscription. ” every day. Learn more.

Software Review 26

Software Review Underperforming Technical Team 2022 Software 26

Workzone

APRIL 23, 2020

It helps your team build the foundation, processes, and discipline needed to drive project management success. Proofhub is an all-in-one project planning software that was launched in 2011. . Check out our top Basecamp alternatives article. Pros: Highly customizable, JIRA can support Scrum, Lean, or Kanban project methods.

Software Review 26

Software Review Underperforming Technical Team Software Technical Review 26

Digite

MARCH 12, 2018

Most people, as well as me, are used to Scrum (or more likely Zombie-Scrum or Scrum-But ), but I believe it is too early to do proper Scrum here. In the usual Scrum process, the P.O. So I will likely implement Kanban (in Jira). What are your best practices here? • One column per person/pair?

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

Workzone

AUGUST 4, 2021

So if you’re not sure it’s the right fit for your team, then this article will help you find the right Asana competitors. No other software on the market offers such an extensive onboarding and training process included with their subscription. Launched in 2011, Proofhub is an “all-in-one” project planning software.

2021 26

2021 Software Review Technical Review Underperforming Technical Team 26

Workzone

JULY 23, 2021

Before Workzone, we had no process for the trafficking of jobs. Zoho Projects is a Project Management component of Zoho, which offers a series of products to help mid-range to large organizations with their business processes. Workfront scales with the growth of organizations, helping establish processes along the way.

2021 26

2021 Software Review 2002 Technical Review 26

Herding Cats

OCTOBER 20, 2017

The sequence of the work processing can be any order: First in First out, Last in First out, or any other or even a random sequence in your workflow. What is the process? . What are the steps in the process? But what if we're trying to decide what throughput is needed for some process in the future. 1988), 308-323.

Underperforming Technical Team 34

Underperforming Technical Team 2008 Software Developers Software Development 34

Wrike

NOVEMBER 7, 2018

Need up-to-date facts and figures for a project management report, article, or infographic? Having a knowledge transfer process in place boosts the chance of project success by over 20%. [6]. Most Popular Agile Tools and Processes: Scrum – 43%. Poor purchasing processes: 23%. 18% use word processing documents.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

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

Scrum.org

FEBRUARY 14, 2022

In my Professional Scrum Training and coaching sessions with teams, I’m often asked about how to navigate organizations’ centralized planification. In this article, I'll share an alternative to traditional organizations’ top-down structures - DAOs. How do DAOs support Scrum Teams?

Agile 233

Agile Underperforming Technical Team 2011 SCRUM 233

Herding Cats

NOVEMBER 7, 2016

The same process for estimating is applied to multi-billion dollar projects we work. 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. 5 Oct 1990, Page 21. 8, August 1995. 400-407, 2009.

Estimate 64

Estimate 2006 2005 2013 64

International Institute for Learning

SEPTEMBER 20, 2022

Academic literature and the web are full of interesting articles giving reasonable and shareable advice to inspire the leaders. For instance in the Agile Scrum Methodology [4] it is recommended to have 10 or fewer people in a team. 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