Scrum.org

MAY 26, 2020

TL; DR: The Agile Movers & Shakers Interview w/ Christiaan Verwijs & Barry Overeem. If so, you can subscribe here and join 26k agile peers. The Agile Movers & Shakers Interview with The Liberators Christiaan Verwijs & Barry Overeem. What brought you to ‘agile?’. Christiaan : A friend of mine started a software company.

Agile 102

Agile 2004 SCRUM Software Developers 102

Inloox

DECEMBER 3, 2020

The creators of Scrum , Ken Schwaber and Jeff Sutherland, developed the concept in the early 1990s. In 2010, they published the first Scrum Guide, a guide to the method with the intention of providing people, teams and organizations with a framework to master complex tasks and create products with the highest possible value.

2020 130

2020 SCRUM 2010 2017 130

Digite

JANUARY 7, 2018

262 pages, ET to read: 4 hours, Published April 7th, 2010 by Blue Hole Press). This is the original book where David Anderson first laid down the definition of and guidance to the Kanban Method for software and knowledge work. David Anderson, who is widely regarded as the Kanban Method pioneer published this book in 2010.

Lean 79

Lean Software Review 2010 2014 79

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

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. Jeff Sutherland and Ken Schwaber moved the development of Scrum forward in the early 1990s. Ken Schwaber first documented Scrum in 1995 in the paper “ SCRUM Development Process.”

SCRUM 110

SCRUM 2003 2010 2013 110

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

MARCH 17, 2019

Here are my collected works, presentations, briefings, journal papers, articles, white papers, and essays, used to increase the Probability of Project Success (PoPS) I've developed and applied over my career in the software-intensive system of systems domain. Agile Project Management. A paradigm of Agile Project Management.

2003 54

2003 2011 2008 Performance Measurement 54

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. IEEE Transactions on Software Engineering , Vol. 255, April 2010. 24, 2010. “A México, 1 al 3 de Febrero de 2006.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

OCTOBER 5, 2018

The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ? This variation can be explained by the fact that initial concepts do not describe the final software system accurate enough.

2012 48

2012 2007 2011 2010 48

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. IEEE Transactions on Software Engineering , Vol.

Risk Management 35

Risk Management Risk Technical Review 2002 35

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

MARCH 11, 2017

The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. This is the motivation for short work intervals found in agile development. . Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E.

2003 46

2003 2014 2015 2011 46

Project Pulse Journal

MARCH 25, 2024

Organizational agility relies on the capabilities of the individuals led and managed by agile product managers and project managers. The development process of products and the project lifecycle integrate to deliver the perceived value to stakeholders.

Sustainability 52

Sustainability Innovation Development Team Review 2024 52

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. can compensate for a mediocre Scrum Master and Product Owner.

SCRUM 141

SCRUM 2002 2003 2001 141

ProjectManager.com

MARCH 4, 2022

The scrum methodology was developed as a response to rigid project management approaches such as the waterfall method, which didn’t adapt to the needs of agile product and software development teams. Scrum is part of agile software development and teams practicing agile. Learn More!

SCRUM 337

SCRUM Software Review Development Team Review Underperforming Technical Team 337

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. The Cone of Uncertainty,” Stephen Gryphon, Phillippe Kruchten, and Steve McConnell, Letters, IEEE Software , 23 (5) 2006, pp 8?10.

2012 29

2012 2007 2010 2006 29

Herding Cats

NOVEMBER 14, 2018

When we hear of the difficulties of making decisions in the presence of uncertainty, especially about software features and capabilities, there are straightforward ways to solve this problem. AHP was developed in the 1970s by Dr. Thomas Saaty. In our agile software development world, AHP is rarely found.

Technical Review 47

Technical Review 2010 2014 Software Developers 47

Herding Cats

DECEMBER 3, 2017

Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. And if the competitor is shipping software with greater value, how does the Cone impact that? 37-48, 2007. 37-48, 2007. Thesis, University of Southern California, August 2012.

2007 34

2007 2012 2009 2010 34

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

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. The Standish report: does it really describe a software crisis?" Laurens Eveleens and Chris Verhoef, IEEE Software , vol. Standish Report.

2006 28

2006 2010 Estimate Agile 28

Herding Cats

JANUARY 9, 2017

The idea of risk and its management and handling is a critical success factor for all software development. Peter Drucker (1975) Management (From The Principles of Software Engineering , Chapter 6, Tom Glib, 1988). 1] Control or Economic Law Paperback, Eugen von Boehm-Bawerk, 2010. [2] Related articles. What is a Team?

Estimate 28

Estimate Risk 2010 Software Engineering 28

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? Visibility.

Software Review 36

Software Review Technical Review 2005 SCRUM 36

Herding Cats

APRIL 8, 2017

Much of the conversation in social media around agile techniques seems to be based on the differences between the variety of choices of a method, a process, or a practice and definitions of terms for those choices. These systems fall into the Software Intensive System of Systems (SISoS) category.

Web Development 37

Web Development Software Engineering Engineering 2010 37

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.

2020 38

2020 Software Review Technical Review Software 38

Herding Cats

MARCH 11, 2018

Microeconomics is applicable to the development is software systems. If we look at the discipline of software engineering, we see that the microeconomics branch of economics deals more with the types of decisions we need to make as software engineers or managers. Software engineering economics." Boehm, Barry W.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Project Management Hacks

AUGUST 4, 2016

Through many discussions with my husband – who works in software development – I discovered an interest in the technology field. I led an effort to develop a risk-based software development process. We developed the process with input from the user community, including business partners as well.

2013 28

2013 2003 Technical Review 2010 28

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. ASE’10, September 20–24, 2010, Antwerp, Belgium. . [8] Software Engineering Economics”. Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10] Agile Estimating and Planning, Prentice-Hall, 2005. [12] IEEE Software, March-April 2009, pp.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. ASE’10, September 20–24, 2010, Antwerp, Belgium. . [8] Software Engineering Economics”. Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10] Agile Estimating and Planning, Prentice-Hall, 2005. [12] IEEE Software, March-April 2009, pp.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

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! your project team).

Artificial Inteligence 122

Artificial Inteligence Critical Chain Underperforming Technical Team Agile 122

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. ASE’10, September 20–24, 2010, Antwerp, Belgium. . [8] Software Engineering Economics”. Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10] Agile Estimating and Planning, Prentice-Hall, 2005. [12] IEEE Software, March-April 2009, pp.

Technical Review 28

Technical Review Estimate 2005 Software Review 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 175

Underperforming Technical Team 2007 2006 2009 175

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

nTask

AUGUST 8, 2019

This helped us to simplify how nTask project management software can be used for solving such issues. Its simplicity and ease of implementation has made it the most popular version of the systems development life cycle (SDLC) for software engineering and IT projects. Waterfall is a popular SDLC project management model.

Software Review 97

Software Review 2019 Development Team Review Technical Review 97

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

APRIL 16, 2019

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Agile Project Management (#APM). Agile Software Development (#ASD).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

APRIL 4, 2019

Research shows that for projects, especially software projects Aleatory uncertainty is the predominant source of risk. So here are some books, handbooks, and guides that sit on my shelf that are used pretty much all the time on the Software Intensive System of Systems we work on. Software Risk Management , Barry W.

Risk Management 43

Risk Management Risk 2003 2011 43

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. Being able to track the time associated with each and every project is one of the most critical aspects of a project management software. They are: 1. Key Features.

2019 111

2019 2006 2010 Software Review 111