Ron Rosenhead

SEPTEMBER 17, 2015

It is called “Initiating successful projects” and was first published in December 2011. We are therefore re-focusing our studies earlier in the project lifecycle to better assess the quality of, and to influence successful, project initiation. The report goes on to suggest: “….our Why not take a look at the report?

2011 188

2011 Transportation Governance Government 188

Scrum.org

OCTOBER 19, 2022

But adherence to a framework or prescribed process does not guarantee agility. Adherence to a framework or prescribed process does not guarantee agility.”. I prefer a process-based definition of agility. Although we used Scrum teams for our investigation, these processes are generic enough to apply to Agile teams in general.

Agile 206

Agile 2010 2013 2008 206

Scrum.org

FEBRUARY 25, 2021

Top-management is actively involved in the process, decisions are being made according to evidence. Being involved in the Agile transformation process means that executives not only support but they make important decisions as a result of the inspection of the current situation. Clear goals make the process understood and transparent.

Agile 137

Agile Lean 2011 2015 137

Herding Cats

MARCH 17, 2019

Managment Processes. Making the Impossible Possible: Applying Heliotropic Abundance for creating Program and Project Management Processes. Establishing the Performance Measurement Baseline (PMB) , AACE Workshop, Denver, Colorado, April 16, 2011. Establishing the Performance Measurement Baseline , AACE Workshop , April 16, 2011.

2003 54

2003 2011 2008 Performance Measurement 54

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. These topics influence all domains. .

Agile 98

Agile Lean 2011 SCRUM 98

Scrum.org

MAY 29, 2020

The reason in 2011, Gojko Adzi introduce a different name to group these practices - “ Specification by Example ". This influence on software design and architecture became so important, beside the other positive effects, that Beck found it worthwhile to rename it from Test-First Programming to Test-Driven Development. Add a test.

Software Review 133

Software Review Technical Review 2004 2003 133

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

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

Epicflow Blog

MAY 14, 2019

Most organizations build structures and processes designed to prevent project failure. However, Muratgali Karimsakov , a Project Engineer at Karachaganak Petroleum, warns that lessons learned must be applied in the right way: “Unfortunately, the lessons learned process in many companies doesn’t work properly.

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75

Online PM Courses

FEBRUARY 5, 2018

systems and processes. to… notice outside influences. Solid processes that limit the scope for human error. Processes that Create Good Situational Awareness. Processes that Create Good Situational Awareness. As a project manager, your responsibilities include creating processes that help you to.

Underperforming Technical Team 68

Underperforming Technical Team Risk Management Risk 2011 68

Stepping Into Project Management

MARCH 10, 2014

Today we interview Siddhartha Govindraj, who specializes in Lean/Agile processes for software development. He was nominated for the Brickell Key award in 2011, an award given by the Lean Software & Systems Consortium for recognizing achievements in the lean-agile industry and is also a Fellow of the Lean Systems Society.

2011 37

2011 Lean 2013 Agile 37

Scrum.org

AUGUST 17, 2020

Ross & Nisbett (2011) offer an extensive overview of research in this area. . Initially coined by cognitive psychologist Lee Ross (1977), it happens when people underestimate the influence of the situation on the behavior of others while overestimating the influence of their personal traits and beliefs (Berry, 2015).

2015 219

2015 2014 2004 Influencer 219

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

Planio

JULY 9, 2020

There’s a reason startups are obsessed with “community” and influencers tell you to find your “tribe”. While task management app Wunderlist was released in 2011 and, after being acquired by Microsoft, was discontinued in May 2020. For some people, the process we just outlined for setting up Redmine might sound like a walk in the park.

2006 88

2006 2007 Closing Agile 88

Scrum.org

JUNE 24, 2022

Its earliest members, like Herzberg, started to investigate how the psychological processes of workers influenced their motivation. Autonomy : the autonomy that people have to schedule and perform their work as they see fit, including the process by which to execute it. Self-Determination Theory does not require this.

SCRUM 184

SCRUM 2002 2006 2007 184

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 164

Underperforming Technical Team 2007 2006 2009 164

Scrum.org

FEBRUARY 4, 2022

This post is for anyone who wants to inspire, change or influence others through their efforts as professionals, with emphasis on the latter. I think you should read this post, and take it to heart when you write content that is aimed at influencing others. Academic journals vary in how strict their peer-review process is.

Agile 189

Agile Software Review Underperforming Technical Team Technical Review 189

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

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

Scrum.org

DECEMBER 23, 2021

And in that analogy, refactoring is the process by which that debt is repaid. 2011, Politowski, 2020). I suspect that time pressure and pressure from management have a substantial influence. The higher it gets, the more interest you pay. Technical debt is easily introduced, but not always repaid quickly.

Software Review 180

Software Review Technical Review Underperforming Technical Team 2015 180

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

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

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. “The

Estimate 64

Estimate 2006 2005 2013 64

Teamweek

JULY 12, 2023

TL;DR – Key Takeaways Leadership skills are the abilities and qualities that enable individuals to guide and influence others to achieve common goals, regardless of their role in the organization. How well do they Persuade and Influence? Great leaders can have different leadership styles. What are leadership skills?

Leadership 52

Leadership Development Team Review Underperforming Technical Team Influencer 52