International Institute for Learning

JUNE 2, 2022

Rubin obtained his Certified ScrumMaster (CSM) designation in 2007 and has been teaching Agile and Scrum to enterprise organizations since 2014. I’m one of the few trainers who got the CSM certification early on [2007]. I do think hybrid models are going to be the norm, although no one wants to define what does this look like.

Agile 59

Agile Aerospace 2007 Telecoms 59

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. Risk Management is essential for development and production programs.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Scrum.org

MAY 6, 2022

For example, one exercise focuses on the Definition of Done and how it reduces the risk of complex work. Here too, actions often remain unclear and vague, like “Define stakeholders”, “Go to meetups” or “Focus on Sprint Goals”. Throughout the training, we ask people to identify actionable improvements based on what they learned.

Underperforming Technical Team 158

Underperforming Technical Team SCRUM 2007 Defining 158

Epicflow Blog

JANUARY 12, 2021

Portfolio Office Manager (PfM) is an employee who administers projects and programs in a portfolio in terms of risk, benefit, and performance management and reports on the results to the portfolio director and often workes together with a portfolio office analyst. The industry a PM works in defines the specifics of projects. .

PMO 82

PMO 2007 Controlling Construction 82

The IIL Blog

JULY 19, 2023

2002) define work engagement as a positive, fulfilling, work-related state of mind characterized by vigor, dedication, and absorption. The focus was on traditional projects that began with well-defined requirements. Many of these projects began with just an idea rather than well-defined requirements accompanied by a business case.

2002 78

2002 2023 Leadership 2007 78

Scrum.org

SEPTEMBER 23, 2019

Regarding the job description of the Scrum Master, the Scrum Guide is only comprehensive at a meta-level but rather vague at a tactical level, following its “specific tactics for using the Scrum framework vary and are described elsewhere” approach: The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide.

Development Team Review 135

Development Team Review SCRUM Software Review Technical Review 135

Rebel’s Guide to PM

SEPTEMBER 26, 2016

In parallel, organisations demand greater project collaboration capabilities to deal with more challenging projects and improved portfolio analytics to better manage portfolio risk but cannot find an all-in-one tool to satisfy all their needs. The implementation strategy requires having a plan with the final objectives defined.

Software Review 150

Software Review Software Technical Review PMI 150

Rebel’s Guide to PM

APRIL 8, 2016

You won’t know if the risk log is sound and the resource planning sensible until you investigate. Projects should have objectives that result in clearly defined outputs and benefits. Action if the answer is No: Ask the project sponsor to hold a workshop on defining this and providing ultimate clarity for everyone.

PMO 150

PMO Governance Government 2007 150

Herding Cats

OCTOBER 5, 2018

The Cone of Uncertainty is a useful approach to defining the expected range of uncertainty at specific stages in a project. Coping with the Cone of Uncertainty: An Empirical Study of the SAIV Process Model,” Da Yang, Barry Boehm, Qing Wang, and Mingshu Li, ICSP 2007, LNCS 4470, pp. 37–48, 2007. IT Risk Management.

2012 48

2012 2007 2011 2010 48

Online PM Courses

JULY 23, 2018

PRINCE2 was updated in 2007 , by the way. To help you with scoping – and all other aspects of Project definition, take a look at our Project Manager’s Project Definition Kit – an innovative course and resource kit, so you can take a jumble of ideas, needs, and requests and turn it into a well-defined project.

Risk Management 81

Risk Management Prince2 Controlling Risk 81

Project Pulse Journal

APRIL 15, 2024

Beck, facing the challenges of a high-risk project with dynamic requirements, sought to improve the software development process and practices, leading to the creation of XP. XP was developed in the late 1990s by Kent Beck during his work at the Chrysler Corporation.

Software Review 52

Software Review Technical Review Agile SCRUM 52

nTask

MARCH 10, 2021

It took until 2007 for the Definition of Done (DoD) to be a widespread full-fledged practice. The DoD has been defined by Scrum.org as “ a shared understanding of expectations that the increment must live up to in order to be releasable into production. This is where the DoD comes into play. Managed by the development team. ”.

Software Review 78

Software Review Technical Review 2002 2007 78

Ganttic

OCTOBER 23, 2016

Each variation of “homemade” tools lead to a greater risk of human error, redundant work, file overwrites, multiple versioning etc. So as soon as you define what's the ideal course for the project to go, you can expect that to change. Ekaterina writes about event industry since 2007, she was one of the first authors at eventmarket.ru

Software 60

Software Planning 2007 Logistics 60

Herding Cats

DECEMBER 3, 2017

The planned uncertainty not only needs to decrease over time passing, but this reduction diminishes any impacts of risk on the decision-making processes. First, the Cone of Uncertainty is a Principle used to define the needed reduction in the variances of estimates on Programs. 37-48, 2007. IT Risk Management.

2007 34

2007 2012 2009 2010 34

Planio

JULY 9, 2020

And since 2007, that community has included the Planio team! With literally thousands of professional developers examining the code, the result is software that’s protected against any risk you can imagine. Trackers are how you define or categorize your issues. Reliability. Now it’s time for some tasks!

2006 88

2006 2007 Closing Agile 88

Planio

JULY 22, 2020

Risk Up Front: Managing Projects in a Complex World. To make a complex practice like project management simpler, the most recent version of the PMBOK breaks the core project management processes down into five sections: Initiating : Defining a new project or a new phase of an existing project. Influence: The Psychology of Persuasion.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

Herding Cats

NOVEMBER 18, 2017

1] This is the foundation of Capabilities Based Planning, The Capabilities must be defines before the Requirements are elicited. IT Risk Management. The requirements process begins with the analysis and elicitation of the objectives and constraints of the organization needed to meet the strategic goals in the form of Capabilities. [1]

2007 31

2007 Software Engineering Engineering Manufacturing 31

Herding Cats

JANUARY 22, 2017

Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance. A critical success factor for all project work is Risk Management.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance. A critical success factor for all project work is Risk Management.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance. This is done by active risk management, through probabalistic decision-making.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

APRIL 16, 2019

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Risk Management (#RM). The overarching theme is focused on defining what Done looks like, assessing progress toward Done in units of measure meaningful to the decision makers. Business, Technical, Systems, Risk, and Project Management.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Scrum.org

AUGUST 28, 2020

From the mechanical perspective, change is defined in terms of modifications to structures and processes. Examples of this are individual reward systems, the use of force (change or risk getting fired), and “management by objectives” (Drucker, 1954). For the purpose of this post, I focus on how they approach and understand “change”.

2012 153

2012 2006 2011 Influencer 153

Herding Cats

JUNE 19, 2017

Uncertainty creates Risk. Risk management requires active reduction of risk. These activities, their releationships and values are defined in a PLAN for increasing the probability of success for the project. These topics are connected in a simple manner. All project work is uncertain (probabilistic and statistical).

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Resource Guru

JUNE 23, 2023

Plus, the risk of human error is just far too great. The issue with task-based project management tools is that you run the risk of ignoring resource availability and capacity before assigning tasks. Define stages, assign roles, and set up automated actions within workflows. 15 years later, they boast over 2 million users.

Software Review 52

Software Review Technical Review Software 2021 52

Herding Cats

NOVEMBER 5, 2018

In a previous post, Why Johnny Can't Estimate , mentioned some resources for estimating, the principles of business and technical management that demand estimates be made to make decisions, and background on the sources of uncertainty, that create risk, that require estimating to increase the probability of project success. 325-330, 2013.

Software Review 34

Software Review Technical Review Estimate Software Developers 34

Herding Cats

DECEMBER 4, 2017

Value to the business can be defined using these measures. Assess design progress, Define compliance with performance requirements, Identify technical risk, Are limited to critical thresholds, Include projected performance. Reinventing Project Management , Aaron Shenhar and Dov Dvir, Harvard Business Press, 2007.

2005 37

2005 Performance Measurement Closing Controlling 37

Velociteach

APRIL 27, 2023

Can you define them for us? This really came out of a piece of academic work called “Social Judgment Theory” that was codified around 2007 by Amy Cuddy, Susan Fiske, and Peter Glick. The way I define it for people in professional settings is that it’s really an idea that someone understands your concerns. BILL YATES: Fantastic.

Leadership 70

Leadership Technical Review Underperforming Technical Team Energy 70

MPUG

JULY 17, 2020

What the network chart shows you is the groups or the phases you’ve defined and then the tasks that you listed under each of those phases. That’s happened automatically based on the dependency you defined. You can do that either in a network chart of Schedule Pro or the Gantt chart. Kyle: Great. Thanks Jim.

Software Review 52

Software Review 2014 Planning Technical Review 52

MPUG

OCTOBER 9, 2019

There is a lot, even if you look at PMI or you look at Prince2, there’s a lot that you go through in defining requirements, creating risk plans. You define your roles and responsibilities. There’s just so many variables that it is very difficult and you can’t spend a lot of energy around that.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

MPUG

OCTOBER 24, 2019

I can define the board status where it is, where it has, and I’ve got that whole sheet view to work with.” So I can actually come in and say, “Well, I’m kind of interested in making sure that we have our issues and risk being tracked.” What are my risks? This is where they can come in.

Agile 40

Agile Technical Review Software Review Underperforming Technical Team 40