Scrum.org

MAY 26, 2020

TL; DR: The Agile Movers & Shakers Interview w/ Christiaan Verwijs & Barry Overeem. Christiaan and Barry are both Professional Scrum Trainers (PST) with Scrum.org, dedicated early adopters of Liberating Structures, and co-authors of the upcoming Zombie Scrum Survival Guide. What brought you to ‘agile?’.

Agile 102

Agile 2004 SCRUM Software Developers 102

Scrum.org

AUGUST 22, 2019

Early September a new book will be added to the Professional Scrum Series : Agile Leadership Toolkit - by Peter Koning. Agility is turning the world upside down. Agile leadership is the future. Scrum, Less, and other agile methodologies promise motived, collaborative, and highperforming teams.

Leadership 96

Leadership Agile 2004 Underperforming Technical Team 96

The IIL Blog

AUGUST 8, 2023

Articles are now appearing addressing burnout specifically in a project management environment [Verma (1996), Haynes and Love (2004), Richmond and Skitmore (2006), Pinto et al., 2014), and Jugdev et al., There are more options available for correcting project work-related issues. REFERENCES Freudenberger, H. Staff burn-out. Haynes, N.S.,

Underperforming Technical Team 78

Underperforming Technical Team 2004 2005 2006 78

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 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. 920, November 2004. 3 September 2004, Heiot Watt University, Association of Researchers in Construction Management , Vol. 255, April 2010.

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. 920, November 2004. 3 September 2004, Heiot Watt University, Association of Researchers in Construction Management , Vol. 255, April 2010. Talat Birgonul, and A.

Risk Management 35

Risk Management Risk Technical Review 2002 35

ProProfs Project Management

JANUARY 15, 2021

Anderson was the first person to implement this kanban approach to project management to their IT, Software Development, and knowledge work in 2004. To become agile, it is important to implement the feedback loops. Q1: Is Kanban better than scrum? Q2: What is the difference between a Scrum board and a Kanban board?

Software Review 81

Software Review Technical Review 2004 SCRUM 81

Gunther Verheyen

FEBRUARY 27, 2024

In the summer of 2019 I got in touch with O’Reilly Media about their ambition to add a book about Scrum to their “97 Things” series. For that reason I did not want any specific Scrum accountability in the title.

SCRUM 71

SCRUM 2004 Software Review 2019 71

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. Cognitive paradigms, applied to Scrum / Agile. When a Scrum Team starts work on a Sprint (e.g.

2002 211

2002 SCRUM 2007 2003 211

Herding Cats

MARCH 11, 2017

This is the motivation for short work intervals found in agile development. . Using the Agile Methodology to Mitigate the Risks of Highly Adaptive Projects,” Dana Roberson and Mary Anne Herndon, 10 th Annual CMMI Technology Conference And User Group , November 5 – 8, 2012, Denver, CO. The probability of something happening.

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. What was that, probably 2004, or ’05 or something in that kind of range, I think?

Agile 103

Agile Fractional CTO CTO Hire Influencer 103

Scrum.org

AUGUST 17, 2020

See how approaches like the Scrum Framework and Liberating Structures can prevent some of these biases by bringing in diverse voices and by validating your assumptions against reality. For me personally, it's one of the reasons why I like the Scrum Framework , as it gives guide-rails to help us think and validate our assumptions with data.

2015 225

2015 2014 2004 Influencer 225

Scrum.org

JANUARY 27, 2021

Audience: Scrum Masters , Leaders. This was the birth of the Agile movement with the Scrum Framework (1993), the Agile Manifesto (2001), and later Kanban (2004). Agile Manifesto, 2001. Read: The Scrum Guide. The Scrum Guide. Reviewer(s): Russell Miller PST. Subscribe to A Wee Dram!

2001 217

2001 Software Review Technical Review Underperforming Technical Team 217

MPUG

DECEMBER 3, 2021

He joined Edwards in 2004 as a project coordinator and scheduler and provided project planning and scheduling support to variety of commercial and federal government clients. If you are using agile, you’re not going to necessarily have a lot of requirements at once. Walter’s certifications include the PMP and MCTS.

Software Review 52

Software Review Technical Review Underperforming Technical Team Risk Management 52

Herding Cats

APRIL 4, 2019

Paul Chavas, Elsevier Academic Press, 2004. Agile Risk Management and DSDM Pocketbook , Alan Moran, IARM. Agile Risk Management and Scrum , Alan Moran, Institute for Agile Risk Management, 2014. Effective Opportunity Management for Project: Exploiting Positive Risk , David Hillson, Taylor & Francis, 2004.

Risk Management 43

Risk Management Risk 2003 2011 43

nTask

NOVEMBER 20, 2020

In 2004 this system was adopted by David J. Simply put, Kanban is an agile methodology and is a system for work management. Following scrum ? Taiichi Ohno , an industrial engineer from Toyota Motors – Japan, is credited with creating the first Kanban system. Waterfall ? Or, any other work management methodology ?

2004 60

2004 Engineering Agile Executing 60

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). Agile Project Management. Agile and all SW development operates in the presence of uncertainty.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 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. 61, September 2004. 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

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