Scrum.org

JUNE 1, 2022

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Specifically for Agile teams, Whitworth & Biddle (2007) found that commitment to team goals increases cohesion, team effectiveness, knowledge sharing, and feedback processes. The social nature of agile teams. References.

SCRUM 231

SCRUM 2007 2003 2006 231

LiquidPlanner

MAY 24, 2022

A risk-intelligent organization will employ systems and project tools that protect resilience and value agility. 2003, September 25). If project outcomes are not becoming increasingly predictable, this should trigger an escalation that prompts broader management awareness and possible intervention. Hillson, D. Layton, Mark.

Risk Management 158

Risk Management Risk 2003 2007 158

Binfire

FEBRUARY 8, 2020

Support Agile methods. Wrike- Founded in 2003, it is one of the oldest cloud-based project management app. Support for Agile Method. ?. ?. ?. ?. File Versioning. Portfolios. Data export. Data Import. Activity Log. Custom Links. Mentions (@name). Markup/proofing. Interactive Whiteboard. Time tracking . Markup/Proofing. ?.

2020 164

2020 Software Review 2003 2006 164

Gunther Verheyen

JANUARY 27, 2021

In October 2003 my life of Scrum started, albeit not with Scrum. 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. In April 2011, Ken came to Brussels for an event I co-organized for the Agile Consortium Belgium.

SCRUM 103

SCRUM 2012 2010 2011 103

Rebel’s Guide to PM

JULY 31, 2017

Stefan wrote a popular project management blog and suggested a BarCamp for project managers based on a participant-driven conference hosted by publisher Tim O’Reilly for the IT industry in 2003. Klaus Hofeditz. Further information and registration can be found on the website [link]. These were the themes.

2003 193

2003 2009 2008 2011 193

Herding Cats

MARCH 17, 2019

Agile Project Management. Agile Software Development for Government Software Intensive System of Systems (SISoS) , Boulder Agile Meetup, 27 July 2016. Integrating Agile Software Development with Earned Value Management , College of Performance Management, IPM Workshop, 2015. Integrating Agile with EVM , EVM World, 2013.

2003 54

2003 2011 2008 Performance Measurement 54

Gunther Verheyen

APRIL 24, 2020

Having worked with Scrum since 2003, I am fascinated by its ever-expanding use, which is not limited to software and (new) product development. Are you ready to start moving your Scrum downfield, push back the old adversary of predictive rigidity and sustainably increase your agility? Gunther Verheyen. independent Scrum Caretaker.

SCRUM 110

SCRUM 2003 2010 2013 110

Gunther Verheyen

MAY 20, 2020

On a personal note, I want to share that my journey of Scrum started in 2003. I don’t know whether it has anything to do with the current crisis sweeping the planet , but I worry seriously how this seems an obsession for quite some people. And I spent 7 years (seven!)

SCRUM 109

SCRUM 2003 2011 2010 109

Gunther Verheyen

MARCH 31, 2021

Somewhere along my journey of Scrum, that started in 2003, I started calling myself an independent Scrum Caretaker on a journey of humanizing the workplace with Scrum. Find all planned sessions of this specific Scrum Values workshop at my webshop. Allow me to share why I created this workshop.

SCRUM 94

SCRUM 2003 Process Planning 94

Gunther Verheyen

DECEMBER 26, 2023

We have three kids (2001, 2003, 2013) of which the two oldest (sons) have a disability ( Duchenne and Down Syndrome ). 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

Herding Cats

SEPTEMBER 24, 2017

SAs an early user (as a FORTRAN 77 developer on Software Intensive System of Systems for Ballistic Missle Defense systems), the principles of Iterative and incremental development, emergent requirements, customer in the loop , and other principles, practices, and processes found in Agile started long before the Agile Manifesto.

2003 56

2003 Process Governance Government 56

Herding Cats

MARCH 11, 2017

This is the motivation for short work intervals found in agile development. . in Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. The probability of something happening. A percentage of that value. And we all know.

2003 46

2003 2014 2015 2011 46

Gunther Verheyen

MAY 19, 2022

Mijn boek beschrijft hoe Scrum concrete invulling geeft aan de Agile mindset ( Hfdstk 1. Het Agile paradigma ), wat de fundamentele spelregels van Scrum zijn ( Hfdstk 2. Mijn eigen reis nam een aanvang in 2003 met de ontdekking en eerste toepassing van eXtreme Programming in combinatie met Scrum.

SCRUM 84

SCRUM 2013 2010 2016 84

Scrum.org

AUGUST 1, 2022

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. We know from research in teams that even light conflict has a negative effect on team productivity (De Dreu & Weingart, 2003). I also include insights from scientific research, as existing models about teamwork can provide a lot of focus.

2004 247

2004 2010 2009 2016 247

Gunther Verheyen

FEBRUARY 26, 2024

I embarked on my Agile journey in 2003 when we wrapped eXtreme Programming in Scrum. Besides having engaged with many teams and organizations I have also created and facilitated many Scrum workshops and classes about various topics for various audiences since then.

SCRUM 74

SCRUM Certification 2016 2011 74

Scrum.org

MAY 24, 2021

Agile Manifesto, Scrum Framework) to change this mindset and put individuals over processes from the outset. First, consider there is a range of variables that influence our performance at the workplace, including, but not limited to: Number of working days and hours (Folkard & Tucker, 2003). There have been numerous movements (e.g.

2003 141

2003 Underperforming Technical Team SCRUM Software Review 141

Scrum.org

MAY 29, 2020

If you’re not already aware, the way you think of testing within an agile approach is fundamentally different to the traditional one. In 2003, Dan North created the JBehave framework to replace Junit to remove any reference to testing and replace a testing vocabulary around a behave one. But let us leave that for another day.

Software Review 145

Software Review Technical Review 2004 2003 145

MPUG

OCTOBER 28, 2019

The stages of time will cover the BC time period, the 1900’s where the root of modern project management was driven by the military, and we’ll end up looking at the ever evolving Agile methodology that more and more project manager are implementing now. They are Waterfall and Agile. I first learned about the Agile model around 2003.

PMI 81

PMI Certification 2003 Engineering 81

Herding Cats

SEPTEMBER 27, 2017

It's a popular misconception of the agile community that Waterfall is used in any domain outside their own personal experience, and Big Design Up Front (BDUF) and Big Bang Development (BBD) are the only alternatives to Agile. . This of course is a misinformed and sometime intentionally misinformed idea used to cloud the conversation.

2003 38

2003 Software Engineering Manufacturing Engineering 38

Tony Adams

APRIL 20, 2019

Adapted from Christensen, “The Innovator’s Dilemma” (2003). How do we move our thinking from high risk, agile thinking, innovative go-to-market, to a more sustained, mainstream approach? When we talk about innovative context, we need to differentiate between platform and breakthrough opportunities. Christensen, C.

Innovation 40

Innovation 2003 2007 Sustainability 40

Tony Adams

APRIL 20, 2019

Adapted from Christensen, “The Innovator’s Dilemma” (2003). How do we move our thinking from high risk, agile thinking, innovative go-to-market, to a more sustained, mainstream approach? When we talk about innovative context, we need to differentiate between platform and breakthrough opportunities. Christensen, C.

Innovation 40

Innovation 2003 2007 Sustainability 40

Herding Cats

MAY 10, 2019

Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003. 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. 105, 2003. “A requires making estimates) ? Making,” T. Aven and J.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Scrum.org

APRIL 29, 2022

Our Agile profession is filled with frameworks. Agile frameworks aim towards increased responsiveness and customer value, and each is basically a variation on the same theme: autonomous teams that work closely with their stakeholders to deliver more value frequently. The hidden assumptions of Agile frameworks.

Agile 232

Agile 2003 Underperforming Technical Team 2018 232

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. Effective Risk Management 2nd Edition, Edmund Conrow, AIAA, 2003. 105, 2003. “A Korte, Reliability Engineering & System Safety , Volume 79, Issue 3, March 2003, pp.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Scrum.org

JUNE 5, 2019

Agile software development started with developers. These days, it seems to be more about Scrum Masters, Agile Coaches, Product Owners, and other “process roles”. Agile software development was started by developers. Way back in 2003, I set up the first continuous integration server at NowOnline. Thiery Ketz? —?played

SCRUM 147

SCRUM 2002 2003 2001 147

Leading Answers

JULY 20, 2018

AI has come a long way since Microsoft rolled out the annoying and not so helpful “Clippy” Office Assistant tool in 2003. Agile tool vendor Atlassian, already provide project assistants that help with budgets, estimates, and sprint management. This gives the impression of interacting with a (currently somewhat) knowledgeable person.

Artificial Inteligence 79

Artificial Inteligence Technical Review 2018 2003 79

Leading Answers

JULY 20, 2018

AI has come a long way since Microsoft rolled out the annoying and not so helpful “Clippy” Office Assistant tool in 2003. Agile tool vendor Atlassian, already provide project assistants that help with budgets, estimates, and sprint management. This gives the impression of interacting with a (currently somewhat) knowledgeable person.

Artificial Inteligence 60

Artificial Inteligence Technical Review 2018 2003 60

Wrike

SEPTEMBER 2, 2009

In my previous post that was also cross posted on CloudAve, I brought up the topic of enterprise agility. My conclusion was: to be agile and adapt quickly to the ever-changing business environment, you need to be able to blend top-down control with bottom-up agility in a “Ying and Yang” style. Probably not.

Agile 42

Agile 2006 2003 2001 42

Leading Agile

MARCH 17, 2021

This is Mike Cottmeyer's talk from AgileIndy 2021 on The Executive's Guide to Why Agile Transformation Fails. Announcer] This is Mike Cottmeyer’s talk from AgileIndy, 2021 on “Why Agile Transformation Fails.” So I got involved with agile back in like 2003 and I was working in this company called CheckFree.

2021 62

2021 Agile Underperforming Technical Team SCRUM 62

Scrum.org

FEBRUARY 3, 2020

Scrum/Agile) are more suitable to deal with complex problems because they are more attuned to our cognitive abilities. A powerful example of the above can be witnessed in termite colonies (Camazine, 2003). Cognitive paradigms, applied to Scrum / Agile. waterfalls) are very likely to fail. New York: Wiley; Camazine S.,

2002 218

2002 SCRUM 2007 2003 218

Herding Cats

FEBRUARY 9, 2018

In 2003, Kahneman stated in a Harvard Business Review article "Delusions of Success," in planning major initiatives, executives routinely exaggerate the benefits and discount the costs, setting themselves up for failure. Let's start with some more resources for making estimates in the presence of uncertainty on agile projects.

Underperforming Technical Team 44

Underperforming Technical Team Estimate 2003 Software Review 44

Project Management Hacks

AUGUST 4, 2016

In 2003, I managed a project to set up a new customer at my company’s data center. My team has adopted the Scaled Agile Framework (SAFe) in the last two years. I realize that Agile is not the right fit for every project, but I’ve enjoyed adding a new approach to my skillset. What industry trends are important to your work?

2013 28

2013 2003 Technical Review 2010 28

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. This corresponds with research on autonomous teams, as well as principles of Agile software development.

Underperforming Technical Team 188

Underperforming Technical Team 2007 2006 2009 188

Project Accelerator News

JANUARY 12, 2024

Worth remembering that, in 2003, LEGO was on the verge of shutting its little plastic doors for good, before its digital renaissance it was on the brink of bankruptcy, but thanks to its digital transformation, just 21 years later, Brand Finance Global includes LEGO in its list of the 500 most valuable brands.

2003 52

2003 2030 Artificial Inteligence Consulting 52

Leading Agile

OCTOBER 3, 2023

And that’s typically how I think about a lot of the talks that I give because everything in the agile communities about doing it and learning from it and sharing with people and getting feedback and figuring out how to do it better and that kind of stuff. What is an Agile Culture So, here’s the end of the talk.

Governance 62

Governance Government SCRUM Agile 62

Kiron Bondale

AUGUST 5, 2018

In 2003, Barry Boehm and Richard Turner coined the acronym C.R.A.C.K. Good agile leads (a.k.a. While there is guidance for scheduling projects following an adaptive lifecycle, Eric has taken a very narrow view of agile delivery. Scrum Masters) might be worth their weight in gold, but they are out there.

Development Team Review 136

Development Team Review 2003 Underperforming Technical Team Influencer 136

Herding Cats

MARCH 30, 2019

Agile software development is framed by a manifesto , a set of 12 principles, several methods. Why This Missing Concept is Important to Agile Software Development? . Agile is the ability to create and respond to change. So What Does This Mean to Agile Software Development? . 5] "What is Agile?" References . [1]

Software Developers 39

Software Developers Software Development Agile Software 39