Gunther Verheyen

MAY 20, 2020

Maybe along the road they took a break, read more, gained more experience with Scrum, and demonstrated other forms of patience, persistence, and belief. On a personal note, I want to share that my journey of Scrum started in 2003. There are so many ways to consider and explain Scrum. And I spent 7 years (seven!)

SCRUM 109

SCRUM 2003 2011 2010 109

Kiron Bondale

APRIL 14, 2019

In an earlier article I’d written about the pros and cons of a Scrum Master or agile lead having deep technical expertise in the solution space but what about a Product Owner (PO)? to describe the attributes of an effective PO and the K in that acronym stands for Knowledge.

2003 189

2003 Innovation Agile Risk Management 189

Scrum.org

JUNE 17, 2021

In this highly engaging speaker session from the Agile Camp Berlin 2021, Jutta Eckstein and Maryse Meinen point out the advantages of creating diverse, cross-functional teams to benefit your customers and your organization. ?? You can sign up here for the ‘Food for Agile Thought’ newsletter and join 31,000-plus other subscribers. ??

2003 152

2003 2007 2021 Software Developers 152

Gunther Verheyen

APRIL 24, 2020

Apparently, it is easy to get stuck at interpreting the rules of Scrum. In the publication “ Moving Your Scrum Downfield ” I have described the six essential traits of the game to help you get unstuck and up your game. These six essential traits are indicative of Scrum coming to life. Every case of Scrum is unique.

SCRUM 110

SCRUM 2003 2010 2013 110

Agilemania

MARCH 30, 2021

Before agile came, several industries like software, aerospace, manufacturing used to follow the waterfall approach. Although that time, the meeting in Oregon didn’t result in the birth of agile methodology; it was the first big step in the history of agile. A New Ideology is Born: The History of Agile Manifesto.

Software Developers 98

Software Developers Software Development Agile Software 98

Gunther Verheyen

MARCH 31, 2021

I have created a new, 3-hours workshop to guide people in the discovery of the value in the Scrum Values. The workshop includes cases I selected from my “Scrum Caretaker Book of Exercises” and will be followed by an informal, 30 minutes after-chat. Find all planned sessions of this specific Scrum Values workshop at my webshop.

SCRUM 94

SCRUM 2003 Process Planning 94

Gunther Verheyen

MAY 19, 2022

Mijn boek Scrum Wegwijzer ( Een kompas voor de bewuste reiziger ) is de Nederlandse vertaling van mijn Engelstalige “smart travel companion” getiteld Scrum – A Pocket Guide. Scrum Wegwijzer 2e druk nu beschikbaar! Dat werd het Engelstalige Scrum – A Pocket Guide (A Smart Travel Companion). Gelukkig maar.

SCRUM 84

SCRUM 2013 2010 2016 84

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 ). My work as an independent Scrum Caretaker via my one-person company Ullizee-Inc is the sole source of money for our family. Scrum is what I do for a living. Let there be no misunderstanding: money is important.

2001 67

2001 2013 2024 SCRUM 67

Scrum.org

AUGUST 1, 2022

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. You can observe implicit coordination in Scrum teams when you look at how work moves across a Scrum board, or on- and of the Sprint Backlog. This is also why the Scrum framework includes the Definition of Done.

2004 242

2004 2010 2009 2016 242

Scrum.org

MAY 24, 2021

Agile Manifesto, Scrum Framework) to change this mindset and put individuals over processes from the outset. We will try to evaluate these sources in a Scrum Team context. Example: As a Scrum Master, you are asked to monitor and report the velocity of the team to the management. Get help from your Scrum Master.

2003 140

2003 Underperforming Technical Team SCRUM Software Review 140

Scrum.org

JUNE 5, 2019

This is what another Scrum Master told me after we took turns during a recent training to share a success story about a Development Team. Agile software development started with developers. These days, it seems to be more about Scrum Masters, Agile Coaches, Product Owners, and other “process roles”. We worked with .NET

SCRUM 143

SCRUM 2002 2003 2001 143

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

Scrum.org

APRIL 29, 2022

Do you start a new Scrum team by explaining the roles, artifacts, and events? Do you rarely consider how to build coalitions and persuade people in power to support your work with Scrum? Are you thinking about the psychological needs of people and how to motivate them to work with Scrum? The strength of this claim varies.

Agile 224

Agile 2003 Underperforming Technical Team 2018 224

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

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

FEBRUARY 3, 2020

Their paper provides useful insights into why the Scrum Framework might be so effective when it comes to managing complex work. Their article inspired me to apply the same insights to Scrum and to extend it with my own. A powerful example of the above can be witnessed in termite colonies (Camazine, 2003).

2002 212

2002 SCRUM 2007 2003 212

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

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

Velociteach

OCTOBER 2, 2023

Since 2003, Jim has been the principal of JP Stewart Consulting, and he’s a certified PMP, and he possesses multiple agile certifications. It’s a young woman becoming a scrum master, and it was just not uninteresting subject matter. So my team was three coaches, so we did everything by the scrum book. So there’s that.

Underperforming Technical Team 90

Underperforming Technical Team Risk Management Technical Review Agile 90

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 179

Underperforming Technical Team 2007 2006 2009 179

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. Scrum Masters) might be worth their weight in gold, but they are out there. While there is guidance for scheduling projects following an adaptive lifecycle, Eric has taken a very narrow view of agile delivery.

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

Herding Cats

APRIL 4, 2019

Oriented Perspective , 1st Edition, Terje Aven, John Wiley & Sons, 2003. Agile Risk Management and DSDM Pocketbook , Alan Moran, IARM. Agile Risk Management and Scrum , Alan Moran, Institute for Agile Risk Management, 2014. Effective Risk Management , 2nd Edition, Edmund Conrow, AIAA, 2003.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

APRIL 16, 2019

Agile Project Management (#APM). Agile Software Development (#ASD). Integrating Agile and Earned Value Management (#AEVM). Agile and Earned Value Management Bibliography of papers, books, and thesis (#Biblio). March 6, 2003. Agile Project Management. Agile Universe , 2002. Management Processes (#MP).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Paymo App

JANUARY 19, 2018

Project management methodologies – Agile, Waterfall, PRINCE2, PRiSM, Six Sigma, Critical Path, and many more. Scrum certifications. Scrum is an Agile framework that’s often used for product management or for software-industry projects. Scrum.org provides assignments that can certify your Scrum knowledge.

2018 111

2018 Prince2 Certification Technical Review 111

MPUG

OCTOBER 24, 2019

Please find below a transcription of the audio portion of Tim Runcie’s Agile Series Part 3 webinar being provided by MPUG for the convenience of our members. I think this is kind of exciting to be learning a little bit more about not only just the Agile disciplines, but the technologies that go together. I think this will be helpful.

Agile 40

Agile Technical Review Software Review Underperforming Technical Team 40

Workzone

AUGUST 4, 2021

Best known as the leader in devOps, JIRA can support Lean, Kanban, and Scrum project management. Jira can create great reports for both roadmapping and agile project management. It supports both Agile and Waterfall project methodologies. Wrike is a project management system created in 2003 by Wrike, Inc. Request a demo.

2021 26

2021 Software Review Technical Review Underperforming Technical Team 26

Wrike

NOVEMBER 7, 2018

Agile Project Management. 19% say Agile techniques. Agile Project Management. 38% of organizations report using agile frequently. [6]. 75% of highly agile organizations met their goals/business intent, 65% finished on time, and 67% finished within budget. Most Popular Agile Tools and Processes: Scrum – 43%.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

Herding Cats

JANUARY 23, 2019

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. Or the companion quote from an Agile thought leader. maybe a read of the resources of Estimating Agile Software Development may help. Using Function Points in Agile Projects.

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

Herding Cats

AUGUST 22, 2018

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. million euro Agile project.”. Agile is about responding to change, over following a plan. It can be a complex as a scrum or scrums strategy map in SAFe 4.2

Estimate 35

Estimate Underperforming Technical Team Technical Review Software Review 35

Herding Cats

FEBRUARY 9, 2019

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. We develop these reference classes using Agile Function Points. For any Agile development tools (Rally, JIRA, Team Foundation Server) have embedded tools for making these charts.

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Herding Cats

MAY 7, 2019

This blog page is dedicated to the resources used to estimate software-intensive systems using traditional and agile development methods. Cost Modeling Agile Software Development,” Maarit Laanti and Petri Kettunen, International Transactions on Systems and Applications, Volume 1 Number 2, pp. Avaramidlis and J. Prakash and V.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

NOVEMBER 7, 2016

And the same process is applied to the Scrum development processes on those projects. . Review on Traditional and Agile Cost Estimation Success Factor in Software Development Project,” Zulkefli Mansor, Saadiah Yahya, Noor Habibah Hj Arshad, International Journal on New Computer Architectures and Their Applications (IJNCAA) 1(3): 942–952.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

SEPTEMBER 19, 2018

This is a Closed Loop Control Systems for managing the performance of a Software Intensive System of Systems, all developed using Scrum. Monte Carlo and Agile Development . My favorite is Agile Monte Carlo. 5] "Monte Carlo Methods for Absolute Beginners," Christophe Andrieu, Advanced Lectures on Machine Learning, 2003. [6]

Technical Review 43

Technical Review 2010 Estimate Software Review 43

MPUG

MARCH 25, 2021

There may be a call for more of an agile approach than a waterfall approach, if you catch what I mean, quote, unquote. When I was making up this slide, once upon a time, I was actually thinking about one of the classes that I gave a while back and think it was around in 2003, 2004, and it was for Help Desk administration.

Technical Review 52

Technical Review Underperforming Technical Team Risk Management Software Review 52