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

Scrum.org

AUGUST 28, 2020

The mechanical perspective draws attention to the structure and processes of organizations. In the end, the internal logic of the mechanical perspective rests on checklists, managerial plans, rules, processes, and numbers. From the mechanical perspective, change is defined in terms of modifications to structures and processes.

2012 155

2012 2006 2011 Influencer 155

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

Herding Cats

JANUARY 8, 2018

When gaps in performance, benefits shortfalls, unanticipated cost, schedule, and performance variances, faulty products, or any undesirable outcome, blame the process, not people. 1] Apollo Root Cause Analysis: Effective Solutions to Everyday Problems Every Time, 3rd Edition, Dean Gano, Atlas Books, 2008. [2] Related articles.

2008 34

2008 2011 Manufacturing Estimate 34

Herding Cats

DECEMBER 16, 2017

Estimating Software-Intensive Systems: Projects, Products, and Processes , Richard Stutzke, Addison-Wesley, 2005. Scaling Lean & Agle Development: Thinking and Organizational Tools for Large-Scale Scrum , Craig Larman and Bas Voode, Addison Wesley, 2008. Software Cost Estimation with COCOMO II , Barry Boehm, et. IT Risk Management.

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

Scrum.org

FEBRUARY 22, 2021

Meanwhile, some ideas have gained buzzword status in the process, causing the occasional collateral damage along the way. This core agile product creation process is agnostic to the product delivery framework, be it Scrum, XP, or any other framework. Think of “MVP.”). Download for free : The Scrum Anti-Patterns Guide.).

Software Review 145

Software Review Technical Review Cadence SCRUM 145

Herding Cats

NOVEMBER 12, 2016

Pink, Drive: The surprising truth about what motivates us (2011). . [2] Alleman, "Product & Process Development Kaizen for Software Development, Project, and Program Management, LPPDE, Denver Colorado, April 2008. [5] Ashkenas, “It’s Time to Rethink Continuous Improvement,” HBR blog [link] (2012). . [3]

Agile 61

Agile 2009 2008 2011 61

Herding Cats

OCTOBER 24, 2018

Root Cause is the fundamental initiating cause on a causal chain leading to a failure of a process which results in a recurrence of the problem. Root Cause Analysis is a systematic documented approach to arrive at the true Root Cause of the process problem. What factors lead to software project failure?” Lehtinen and Mika V.

2014 45

2014 Aerospace 2011 2013 45

EasyProjects

SEPTEMBER 24, 2019

Have you ever seen a chef send a dish out without tasting it several times at every stage of the process? According to the Project Management Institute, agile processes initially slow a team down because of the learning curve. There is no limit to how many stages you can have but make sure that they work well with your process.

Agile 41

Agile Technical Review Software Review Underperforming Technical Team 41

Velociteach

MARCH 20, 2023

In this unique project story, John Holmes explains how he navigated the selection process and became the exclusive supplier of turfgrass for the 2022 FIFA World Cup. We didn’t invent the process, but we somewhat perfected it. And we set off, took off running in 2011. And we’ll get into that process, sure, in a little while.

Logistics 52

Logistics Transportation 2022 Governance 52

MPUG

MARCH 28, 2021

Best Practices : It’s better to send information to too many people than too few, suggests Ron Taylor, founder of the Ron Taylor Group and PMI’s 2008 Leader of the Year. For another example, if a project is going to change how processes in your organization are going to work, you can begin to tout the benefits of the changes.

Planning 90

Planning Underperforming Technical Team Software Review Executing 90

Scrum.org

APRIL 7, 2022

Bushe and Chu (2011) identify seven situations that drive the use of fluid teaming in those environments: High turnover among employees, leading to changes in teams. Even a single change in team membership can disrupt that process, and consequently, make it harder for teams to become high-performing sooner. The need for fluid teams.

Underperforming Technical Team 169

Underperforming Technical Team 2007 2006 2009 169

Scrum.org

AUGUST 17, 2020

Ross & Nisbett (2011) offer an extensive overview of research in this area. . Research (Janiszewski & Uy, 2008) even shows that precise offers (e.g. Survival bias happens when failures are ignored when you are evaluating if a process or decision is the right one (Schermer, 2014). —?like personality, experience, and skills.

2015 222

2015 2014 2004 Influencer 222

The IIL Blog

JUNE 28, 2018

According to management guru Peter Drucker, there are only two sources for growth: marketing and innovation [Drucker, 2008]. Innovation management , in its purest form, is a combination of the management of innovation processes and change management. The change can be incremental or radical.

Innovation 106

Innovation 2008 2011 2010 106

Herding Cats

APRIL 4, 2019

Risk Analysis – A Quantitative Guide , Third Edition, David Vose, John Wiley & Sons April 2008. Risk Analysis: A Quantitative Guide , David Vose, John Wiley & Sons 2008. Henry Montgomery (Editor), Universitetsforlaget; UK Edition, November 28, 2011. 3421, Second Edition, December 2011. Gideon Keren (Editor),?

Risk Management 43

Risk Management Risk 2003 2011 43

Resource Guru

FEBRUARY 7, 2024

Founded: 2011 Customer ratings: G2 4.7/5, Founded: 2008 Customer ratings: G2 4.2/5 Ultimately, depending on what your agency project management processes look like, the tool might be on the simplistic side and not ready to scale as your agency grows. It offers robust workflow automation that streamlines complex processes.

Software Review 52

Software Review 2005 2008 2011 52

Herding Cats

APRIL 16, 2019

Management Processes (#MP). While many of the presentations have similar titles, the content is focused on a specific set of processes and practices, while the principles are the same, since they are Immutable. . Management Processes. Project Success Assessment - A checklist for assessing the processes for project success.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

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. episteme), meaning knowledge of uncertainty due to a lack of knowledge of quantities or processes of the system or the environment.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Teamweek

MAY 21, 2020

Trello started in 2011 as a tool for software development teams. Kanban was first introduced by Toyota to improve its manufacturing processes. Asana was founded in 2008 by ex-Google and Facebook engineers. Toggl Plan (previously Teamweek) started in 2011 as an in-house project for Toggl — a time tracking tool.

2020 52

2020 Planning Software Review 2011 52

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

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. 3, May–June 2011, pp.

Underperforming Technical Team 34

Underperforming Technical Team 2008 Software Developers Software Development 34

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. Launched in 2011, Proofhub is an “all-in-one” project planning software.

2021 26

2021 Software Review Technical Review Underperforming Technical Team 26

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. Google will find these when there is no URL provided.

Estimate 64

Estimate 2006 2005 2013 64