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 228

2004 2010 2009 2016 228

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 98

Agile 2004 SCRUM Software Developers 98

Herding Cats

DECEMBER 16, 2017

The estimating of software development is both straightforward and complex. Here are some resources that will provide guidance to produce credible software development estimates, in both traditional and agile domains. Software Sizing and Estimating: Mk II FPA , Charles Symons, John Wiley & Sons, 1991.

Software Developers 46

Software Developers Software Development Estimate 2006 46

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

MPUG

JANUARY 4, 2021

I’d like to begin by sharing a brilliant quote that puts the latest project management fashion, Agile, into humbling perspective: “ A Waterfall project is just an Agile (Scrum) project with one huge sprint! An Agile project is just a Waterfall project almost entirely implemented using Rolling Wave Planning!

Artificial Inteligence 122

Artificial Inteligence Critical Chain Underperforming Technical Team Agile 122

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 163

Underperforming Technical Team 2007 2006 2009 163

Digite

JANUARY 7, 2018

Several good books have been written on Kanban and its application to various business processes, especially to Scrum, since David Anderson published his original Kanban “blue book”. 262 pages, ET to read: 4 hours, Published April 7th, 2010 by Blue Hole Press). 120 pages, ET time to read 2 hours, Published 1 March 2010 by Lulu.com).

Lean 79

Lean Software Review 2010 2014 79

nTask

NOVEMBER 23, 2018

Introduced in 2006, with a major redesign in 2010, the platform serves as a single systematic and flexible solution for all the task management needs of a team. Considered a #1 software chosen by agile teams for software development, Jira makes a pretty strong contender for Smartsheet. Kanban and Scrum boards.

2019 111

2019 2006 2010 Software Review 111

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. What does this say about Development Teams out there? Agile software development started with developers. Agile software development was started by developers.

SCRUM 139

SCRUM 2002 2003 2001 139

Herding Cats

NOVEMBER 7, 2016

And the same process is applied to the Scrum development processes on those projects. . Believing is Seeing: Confirmation Bias Studies in Software Engineering, “Magne Jørgensen and Efi Papatheocharous, 41st Euromicro Conference on Software Engineering and Advanced Applications (SEAA). Tanilkan, Hans Gallis, Anette C.

Estimate 64

Estimate 2006 2005 2013 64

Leading Agile

NOVEMBER 17, 2020

Listen to the Agile Unplugged Podcast on the go! Find and subscribe to Agile Unplugged on: Apple Podcasts. Welcome to our latest episode of the Agile Unplugged podcast with host Mike Cottmeyer, LeadingAgile’s CEO. So we first worked together, I guess it was probably back in like late 2009, 2010. Soundcloud.

Technical Review 112

Technical Review Software Review Agile Governance 112

EasyProjects

SEPTEMBER 24, 2019

What is Agile Project Management? . That is precisely what agile project management is – taste testing the stew at various points to ensure that it’s tasting the way it should. Agile Project Management Defined. Agile project management is an iterative or incremental approach to completing projects. How to be Agile.

Agile 41

Agile Technical Review Software Review Underperforming Technical Team 41

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. & Zein, S.,

Estimate 40

Estimate Software Review Software 2012 40

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. 255, April 2010. 24, 2010. “A Project Risk Management: Lessons Learned from Software Development Environment,” Y.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Digite

MARCH 12, 2018

Most people, as well as me, are used to Scrum (or more likely Zombie-Scrum or Scrum-But ), but I believe it is too early to do proper Scrum here. Or rather one column per stage for the tasks (i.e., “in development”, “in testing” etc.)? In the usual Scrum process, the P.O.

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

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

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. 255, April 2010. 24, 2010. “A

Risk Management 35

Risk Management Risk Technical Review 2002 35

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

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. David even built on the methodology to define the kanban method and released a book in 2010 called “Kanban: Successfully Evolutionary Change for your Technology Business”.

Software Review 81

Software Review Technical Review 2004 SCRUM 81

Wrike

NOVEMBER 7, 2018

Agile Project Management. Project Management Software & Tools. 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. Other – 6%.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

Herding Cats

APRIL 4, 2019

Misconceptions of Risk , Terje Aven, John Wiley & Sons, 2010. Critical Code, Software Producibility for Defense, Committee for Advancing Software-Intensive Systems Producibility , Computer Science and Telecommunications Board Division on Engineering and Physical Sciences, National Research Council of the National Academies, 2010.

Risk Management 43

Risk Management Risk 2003 2011 43

Wrike

AUGUST 14, 2020

Kanban is one of the most popular Agile project management frameworks around, and for good reason. Agile is a project methodology that promotes tackling projects by breaking them down into smaller stages. There are various frameworks teams can choose to follow to adopt Agile, Kanban being one of them. What is Kanban? Keep roles.

Software Review 36

Software Review Technical Review 2005 SCRUM 36

Herding Cats

DECEMBER 15, 2016

The Standish Report is raising its head again in the Agile presentations I've seen recently at conferences. The Non-Existent Software Crisis: Debunking the Standish Report. Laurens Eveleens and Chris Verhoef, IEEE Software , vol. 1, Jan-Feb 2010, pages 30-36. Standish Report. Standish Report and Naive Statistics.

2006 28

2006 2010 Estimate Agile 28

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). Those lessons are directly transferable to the management of software development teams.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

MPUG

OCTOBER 16, 2019

Please find below a transcription of the audio portion of Tim Runcie’s Agile Series Part 2 webinar being provided by MPUG for the convenience of our members. Kyle: Hello everyone and welcome to part two of MPUG’s Agile training series. Hence Agile, right? My name is Kyle and I’ll be the moderator today.

Agile 40

Agile Technical Review Software Review Engineering 40

Herding Cats

JANUARY 20, 2018

But in the software development world, the domains of IT, there are two other colors of money. There are two types of software that are developed for a business: 1) internal-use software, and 2) software developed to be sold, leased or marketed (“software to be sold”). CAPEX and OPEX.

Software 38

Software 2006 Software Developers Software Development 38

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. Harrison, AIP Conference Proceedings , January 5, 2010, 1204, pp. 247, September 1949, pp.

Technical Review 43

Technical Review 2010 Estimate Software Review 43

Workzone

APRIL 30, 2020

In 2010 daPulse, created by Wix.com , joined the vast array of project management tools on the market, and in 2017, daPulse went through a transformation to become Monday.com. Designed to come across as colorful and friendly, Monday aims to help you kick your case of the Monday blues through the use of its software. Conclusion.

2020 38

2020 Software Review Technical Review Software 38

MPUG

SEPTEMBER 9, 2020

Satya N Dash: You have also agile record concepts coming into time management that you have a lot of additional concepts such as burn up chart, burn down chart, release planning, story map. As early as 2009, 2010, nearly 11 years before I was working as a PMO. You will need a scheduling took, which in our case is Microsoft Project.

Software Review 52

Software Review Critical Chain Technical Review Risk Management 52