Scrum.org

DECEMBER 18, 2020

In the end, the sources I used for describing the evolutions of the definition of Scrum are: The paper “SCRUM Software Development Process” by Ken Schwaber (1995, 1996). The book “Agile Software Development with Scrum” by Ken Schwaber and Mike Beedle (2002). The book “Agile Project Management with Scrum” by Ken Schwaber (2004).

2010 232

2010 SCRUM 2004 2002 232

Leading Answers

AUGUST 9, 2023

Suitability filters are models that offer simplified views of a decision-making process. There are few physical or visible increments in the process. Left unchecked, our mental models of a product, project or process can diverge from our teammates. This comprehensive list post dates from 2007.

Underperforming Technical Team 78

Underperforming Technical Team 2007 Agile PMI 78

Herding Cats

OCTOBER 30, 2018

There have been some recent posts about managing scope, defining needed Features, determining how to release software to stakeholders - in both traditional and agile processes. The primary document produced from the Capabilities Based Planning process is the Concept of Operations.

Planning 109

Planning 2007 Technical Review 2009 109

LiquidPlanner

MAY 24, 2022

A risk-intelligent organization will employ systems and project tools that protect resilience and value agility. Www.irmi.com, July 2007, www.irmi.com/articles/expert-commentary/risk-management-practices-cannot-be-bolted-on. 4 Is your project team empowered to deliver your project and business commitments using best-in-class tools?

Risk Management 158

Risk Management Risk 2003 2007 158

Scrum.org

APRIL 8, 2021

Having urgency is a great motivator and starting point as shown in John Kotter’s 8-Steps process. . . Figure 5 The 8-Steps Process for Leading Change* * [link]. This process for change is mostly applicable for high level strategic goals like company vision and business strategy. This understanding of agile is just wrong.

2007 218

2007 2011 Risk Management 2020 218

Rebel’s Guide to PM

MARCH 15, 2017

The names and processes are different, however, but very results focused. I decided in 2007 to obtain my PMP® and that is when I really become serious about formal project management. I have been in the IT field since I graduated from Eastern Michigan University and was commissioned in the US Army. What is your current role?

2007 304

2007 Governance Government Construction 304

Gunther Verheyen

DECEMBER 17, 2020

In the end, the sources I used for describing the evolutions of the definition of Scrum are: The paper “SCRUM Software Development Process” by Ken Schwaber (1995, 1996) The paper “SCRUM: An extension pattern language for hyperproductive software development” by Mike Beedle, Martine Devos, Yonat Sharon, Ken Schwaber and Jeff (..)

2010 141

2010 SCRUM 2004 2002 141

Gunther Verheyen

JANUARY 27, 2021

In April 2010, at an event of the Agile Consortium Belgium in Brussels, I asked Jeff Sutherland about this new organization founded by his former companion. I had been closely following up on the emergence and growth of Scrum.org as it coincided with a personal process of professional recovery. It intrigued me.

SCRUM 103

SCRUM 2012 2010 2011 103

Scrum.org

FEBRUARY 25, 2020

When I started using Scrum as a software developer back in 2007 I noticed that this new ways of working really worked, then I decided to learn more about and I became a Scrum Master in 2012 and in 2015 I started to teach Scrum, overcoming my fear of public speaking. The moment was perfect in my career.

2017 174

2017 2018 2016 SCRUM 174

ProjectManager.com

DECEMBER 12, 2018

In 2007, PMP was accredited by the International Organization for Standardization (ISO), and as of July 2018 over 876,000 people hold this certification. The organization also offers an ethics complaint and review process as a resource to project managers. They have many articles, papers and webinars on the subject. PMI Events.

PMI 279

PMI Technical Review Certification Software Review 279

Agilemania

FEBRUARY 23, 2023

Concerns were voiced in the IT operations and software development sectors from 2007 to 2008 about the old software development paradigm that split operations from developers regarding how code was distributed and supported. The DevOps technique supports continuous innovation, agility, and scalability. What is DevOps?

Software Review 52

Software Review Technical Review Certification 2007 52

Gunther Verheyen

DECEMBER 26, 2023

It wasn’t when we gave up on my wife’s income to allow her to develop her creative talents (2007). If it was money that drives me, I would have created my own proprietary program of Agile/Scrum classes and a certification scheme when I went independent (which seems to be what many people thought I was going to do).

2001 67

2001 2013 2024 SCRUM 67

The IIL Blog

JULY 19, 2023

The wage and salary activities for the assigned workers were the responsibility of their functional managers and project managers often had very little input if any in the performance review processes. Engagement activities do not end at the completion of the staffing process or shortly thereafter. Pendry et al.,

2002 78

2002 2023 Leadership 2007 78

Herding Cats

OCTOBER 5, 2018

Little [8] makes the claim that agile methods don't follow the Cone - that is the uncertainty doesn't reduce as the project proceeds. The program management processes should seek to reduce uncertainty in the variable of the project. 37–48, 2007. Here's a very short reading list for this topic (88 more items on Request). "A

2012 48

2012 2007 2011 2010 48

Planio

JULY 9, 2020

Agile Project Management out of the box. And since 2007, that community has included the Planio team! The process is a little more complicated than simply installing an app, but as long as you’re familiar with database configuration and can follow instructions, you should be okay. (If Agile Project Management out of the box.

2006 88

2006 2007 Closing Agile 88

Herding Cats

MAY 10, 2019

This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. Project Risk Management: A Combined Analytic Hierarchy Process and Decision Tree Approach,” Prasanta Kumar Dey, Cost Engineering , Vol. 3, March 2002.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

DECEMBER 16, 2017

Here are some resources that will provide guidance to produce credible software development estimates, in both traditional and agile domains. While some have publication dates that may seem old, the principles in these books are immutable, even for agile projects. Agile Estimating and Planning , Mike Cohn, Prentice Hall, 2006.

Software Developers 46

Software Developers Software Development Estimate 2006 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. Project Risk Management: A Combined Analytic Hierarchy Process and Decision Tree Approach,” Prasanta Kumar Dey, Cost Engineering , Vol. 5, September/October 2011. 3, March 2002.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

AUGUST 1, 2018

We're writing two chapters in an upcoming Project Management Book, with a working title, The Gower Handbook of Project Performance for Agile, Waterfall and Everything in Between , edited by Mark Phillips. 37–48, 2007. One chapter on the Principles of Risk Management and the second chapter on the Practices of Risk Management.

2012 29

2012 2007 2010 2006 29

nTask

MARCH 10, 2021

It took until 2007 for the Definition of Done (DoD) to be a widespread full-fledged practice. The first step in ensuring that everyone agrees as well as accepts the DoD you create is by making the process one for the team and engaging the entire team when doing so. Step 1: Use Teamwork to Decide on the DoD.

Software Review 78

Software Review Technical Review 2002 2007 78

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. Google will find each of these for you, as a start to the extensive body of litertaure for estimating agile projects in the presence of uncertainty. 37-48, 2007.

2007 34

2007 2012 2009 2010 34

Online PM Courses

OCTOBER 14, 2018

And we mustn’t forget that there are other widely used hashtags in the #PMOT community, like #Agile, #PMO, and #PMP. We make Agile teams become amazing, check out our free online masterclass: agilesumo.com. Chris’s Article at Online PM Courses: Why You can No longer Ignore Agile Methodologies. Developing Leaders.

PMO 75

PMO Technical Review Underperforming Technical Team PMI 75

Tony Adams

APRIL 20, 2019

We talk a lot about Project Management structure, processes and practices – these are put forward as a way of providing stability and certainty. Shenhar and Dvir (2007) pose an interesting argument about innovation in a project management context. 2007) Managing Projects for Business Innovation. Boston USA. Moore, G.A.

Innovation 40

Innovation 2003 2007 Sustainability 40

Tony Adams

APRIL 20, 2019

We talk a lot about Project Management structure, processes and practices – these are put forward as a way of providing stability and certainty. Shenhar and Dvir (2007) pose an interesting argument about innovation in a project management context. 2007) Managing Projects for Business Innovation. Boston USA. Moore, G.A.

Innovation 40

Innovation 2003 2007 Sustainability 40

Scrum.org

DECEMBER 17, 2021

A few years ago, before the pandemic, I visited an Agile conference in Kyiv, Ukraine. At the very end of it there was a panel discussion with some of the big names in the European Agile world. One of the panelists replied: ‘Why use something that claims to be agile, but is only updated once every 3 years or so’. Why indeed?

SCRUM 196

SCRUM 2007 2020 Innovation 196

Herding Cats

NOVEMBER 18, 2017

The requirements documents (in whatever form) are the basis of the process to verify these needed capabilities with customers and internal or external stakeholders and validates these requirement meet to need strategic intent of the work. [2]. that will be necessary.

2007 31

2007 Software Engineering Engineering Manufacturing 31

Scrum.org

APRIL 7, 2022

Recently, the concept of “fluid teams”, “dynamic reteaming” or “ad-hoc teaming” has gained traction in the Agile community. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Kozlowski & Ilgen (2006) describe this reciprocity as “process begets structure, which in turn guides process”.

Underperforming Technical Team 168

Underperforming Technical Team 2007 2006 2009 168

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. Gano, Atlas Books, 2007. 29 May 2013. 1/2, 2001, pp.

2014 45

2014 Aerospace 2011 2013 45

Scrum.org

FEBRUARY 3, 2020

A while ago, I received an interesting scientific article from Gunther Verheyen titled “Getting Things Done: The Science Behind Stress-Free Productivity” (Heylighen & Vidal, 2007). Scrum/Agile) are more suitable to deal with complex problems because they are more attuned to our cognitive abilities. Limitations of attention.

2002 202

2002 SCRUM 2007 2003 202

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

Leading Agile

MARCH 11, 2020

Agile Unplugged is your chance to explore LeadingAgile’s freshest ideas, mental models, frameworks, and solutions with the people that are actually doing the work of leading large-scale Agile Transformation, out in the field. So, I had never, I’d like heard of Agile, but like, I had no experience with Agile.

Agile 103

Agile Fractional CTO CTO Hire Influencer 103

The IIL Blog

JANUARY 24, 2024

ITIL v2 followed this in 2001, ITIL v3 in 2007, and ITIL 4 in 2019. LEAN processes emerged in 1991, with the Agile Manifesto launched by a group of software engineers in 2001. As ITSM evolved, so did the ways of delivering Information Technology services. Service Integration and Management, aka SIAM, was developed in 2005.

2001 78

2001 2007 2024 Information Technology 78

Herding Cats

JANUARY 22, 2017

The Measure that is modeled in the Cone the variable is the Quantitative basis of a control process that establishes the goal for the performance measure. With this paradigm we have logically connected project management processes with Control System processesIf the variances, created by uncertainty going outside the UCL and LCL.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

The Measure that is modeled in the Cone the variable is the Quantitative basis of a control process that establishes the goal for the performance measure. With this paradigm we have logically connected project management processes with Control System processesIf the variances, created by uncertainty going outside the UCL and LCL.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

The Measures that are modeled in the Cone of Uncertainty are the Quantitative basis of a control process that establishes the goal for the performance measures. Again this is simple statistical process control, using feedback to take corrective actions to control future outcomes - feedforward. Resources. [1] Air Force. [4]

Technical Review 28

Technical Review Estimate 2005 Software Review 28

MPUG

OCTOBER 9, 2019

Please find below a transcription of the audio portion of Tim Runcie’s Agile Series Part 1 webinar being provided by MPUG for the convenience of our members. Kyle: Hello everyone and welcome to today’s MPUG training series, part one, Understanding and Incorporating Agile Project Management. It’s not all or nothing.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

Scrum.org

JUNE 24, 2022

But Scrum and the Agile methodologies it builds on are so much more. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Its earliest members, like Herzberg, started to investigate how the psychological processes of workers influenced their motivation. What motivates teams?

SCRUM 188

SCRUM 2002 2006 2007 188