Scrum.org

AUGUST 1, 2022

It has been linked to higher performance and motivation (Mathieu et al, 2000), increased effectiveness (Kearny, Gebert & Voelpel, 2009), and generally explains a substantial amount of the variance (~19%) in the effectiveness of teams (De Church & Mesmer-Magnus, 2010). Analysis of fault generation caused by stress during software development.

2004 234

2004 2010 2009 2016 234

Scrum.org

OCTOBER 19, 2022

2010) reviewed 28 scientific studies that investigated how Scrum is associated with overall business outcomes. Many studies have identified high autonomy as an important prerequisite for Agile teams ( Moe, Dingsøyr & Dybå, 2010 ; Donmez & Gudela, 2013 ; Tripp & Armstrong, 2018 ; Melo et. 2010, April). Cardozo et. References.

Agile 212

Agile 2010 2013 2008 212

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

MPUG

JANUARY 4, 2021

For at least twenty years and counting, the world around us has become more and more software driven, and, as a result, more digital. Electric vehicles are about 50% software, in terms of value, whereas fossil fuel cars are mostly hardware. Banks have essentially been software developing organizations for a long time.

Artificial Inteligence 122

Artificial Inteligence Critical Chain Underperforming Technical Team Agile 122

Gunther Verheyen

APRIL 24, 2020

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.” In 2010 he initiated the creation of the Scrum Guide. They are the co-creators and gatekeepers of (what is) Scrum.

SCRUM 117

SCRUM 2003 2010 2013 117

Scrum.org

MAY 26, 2020

Barry : Failed software development projects. In 2010 I worked as a project manager for a web agency. I was responsible for managing software development projects. Developers, because of the growing crunch-culture. This wasn’t a success. Everyone was unhappy. So the toolbox is diverse.

Agile 100

Agile 2004 SCRUM 2010 100

Scrum.org

APRIL 7, 2022

Research has linked team cognition to higher performance and motivation (Mathieu et al, 2000), increased effectiveness (Kearny, Gebert & Voelpel, 2009), and generally explains a substantial amount of the variance (~19%) in the effectiveness of teams (De Church & Mesmer-Magnus, 2010). So … stable teams or fluid teams? J., & McLendon, C.

Underperforming Technical Team 171

Underperforming Technical Team 2007 2006 2009 171

Herding Cats

MARCH 17, 2019

Applying Deliverables Based Planning ® To Increase Our Probability of Success , PMI Fort Worth, Chapter Meeting, 15 July 2010. Agile Software Development for Government Software Intensive System of Systems (SISoS) , Boulder Agile Meetup, 27 July 2016. How to Develop Credible Cost & Schedule Estimate.

2003 54

2003 2011 2008 Performance Measurement 54

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 ? Steve McConnell. Quantifying IT Forecast Quality,” J. Eveleens and C. GAO Cost Estimating and Assessment Guide," GAO-09-3SP.

2012 48

2012 2007 2011 2010 48

Herding Cats

MARCH 11, 2017

Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp. Architecting Large Scale Agile Software Development: A Risk–Driven Approach,” Ipek Ozkaya, Michael Gagliardi, Robert L. 12, 2008. “A

2003 46

2003 2014 2015 2011 46

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.

2019 111

2019 2006 2010 Software Review 111

nTask

AUGUST 8, 2019

What Dr. Royce was describing was a flawed model for software development as he argued for a model with multiple iterations or runs. Due to the changing needs of the software development industry and the failure of the linearity of the Waterfall Model in providing early feedback, many version of the Waterfall Model have emerged.

Software Review 97

Software Review 2019 Development Team Review Technical Review 97

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. Tim Menzies, Steve Williams, Oussama Elrawas, Daniel Baker, Barry Boehm, Jairus Hihn, Karen Lum, and Ray Madachy, Software Process Improvement And Practice, (2009).

2007 34

2007 2012 2009 2010 34

Herding Cats

AUGUST 1, 2018

“Reducing Estimation Uncertainty with Continuous Assessment: Tracking the 'Cone of Uncertainty’” Pongtip Aroonvatanaporn, Chatchai Sinthop and Barry Boehm, Center for Systems and Software Engineering University of Southern California , Los Angeles, CA 90089, ASE’10 , September 20–24, 2010, Antwerp, Belgium, 2010.

2012 29

2012 2007 2010 2006 29

Herding Cats

NOVEMBER 14, 2018

AHP was developed in the 1970s by Dr. Thomas Saaty. In our agile software development world, AHP is rarely found. This decision model for software development projects addressed: performance, cost, time, and risk. I came to AHP through a seminar by Dr. James T. A Cardinal number says how many of something there is.

Technical Review 47

Technical Review 2010 2014 Software Development 47

Scrum.org

JUNE 5, 2019

Agile software development started with developers. Agile software development was started by developers. Starting out with a strong focus on website development, I built my first site for them in 2002, first as a freelancer later as an employee. NowOnline started somewhere in 2001.

SCRUM 140

SCRUM 2003 2002 2001 140

Herding Cats

JANUARY 9, 2017

The idea of risk and its management and handling is a critical success factor for all software development. 1] Control or Economic Law Paperback, Eugen von Boehm-Bawerk, 2010. [2] 4] " Risk Management and Agile Software Development ," Glen B Alleman. Herding Cats: Economics of Software Development.

Estimate 28

Estimate Risk 2010 Software Engineering 28

Digite

MARCH 12, 2018

I have often wondered – doesn’t speak too well of us as software professionals! Far too many projects and teams are occupied by far too many crises all through the development/ implementation lifecycle. However, the fact is that software development is a complex activity – perhaps more so than any other type of projects?

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

MPUG

JUNE 20, 2022

Examples are software development, new product development, pharmaceutical clinical studies, telecommunication, research and development, education, and government projects. Starting with the 2010-release, Microsoft Project could find the 19?day SuperProject used multiple algorithms to find the tightest schedule.

2010 52

2010 Aerospace Underperforming Technical Team Governance 52

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

NOVEMBER 5, 2018

In software development, those managing the project have some understanding the market forces (from their marketing departments), the technology (from their engineering department), and how to manage in the presence of Aleatory and Epistemic risk (the managers running a successful firm). Software development is a non-ergodic process.

Software Review 34

Software Review Estimate Technical Review Software Developers 34

Wrike

MAY 23, 2023

I joined the team as a QAA engineer in 2010, the first employee in this role. Together, we have developed a unique quality control system for Wrike, our lovely project management platform, allowing us to deploy product code to production more quickly and without bugs. Hello, everyone! I’m Alexander, and I’m a QAA manager at Wrike.

Engineering 36

Engineering Underperforming Technical Team Controlling Software Review 36

Herding Cats

APRIL 16, 2019

Agile Software Development (#ASD). Those lessons are directly transferable to the management of software development teams. Parametric Project Monitoring and Control - Earned Value is an approach to Performance measurement for monitoring and controlling the progress of software development projects.

Technical Review 42

Technical Review Performance Measurement 2003 Governance 42

Herding Cats

DECEMBER 15, 2016

Laurens Eveleens and Chris Verhoef, IEEE Software , vol. 1, Jan-Feb 2010, pages 30-36. Forgetting even more that "agile" is a bottom-up software development solution. Chaos Report Myth Busters , .

2006 28

2006 2010 Estimate Agile 28

Herding Cats

JULY 24, 2017

It's suggested from observations, the Cone of Uncertainty (CoU) is not a valid model of how uncertainty behaves in software development projects. In all software development businesses, showing up late and over budget has a direct impact on the bottom line. . Thesis, George Mason University, 2010. "An

2007 42

2007 2012 2006 2008 42

Herding Cats

SEPTEMBER 19, 2018

Monte Carlo and Agile Development . There are a number of Monte Carlo Simulation tools for agile software development when you don't have an Integrated Master Schedule, with planned durations, and ranges of values. Harrison, AIP Conference Proceedings , January 5, 2010, 1204, pp. Banks, John Wiley & Sons, 2010. [11]

2010 43

2010 Technical Review Estimate Software Review 43

Herding Cats

APRIL 8, 2017

In many conversations about managing in the presence of uncertainty - which is the ubiquitous condition for all non-trivial software development projects - the notion that principles, processes, and practices of Engineered Systems appear to be the antithesis of Agile development in some quarters. . 39-58, 1997. [3]

Web Development 37

Web Development Software Engineering 2010 Engineering 37

Project Pulse Journal

MARCH 25, 2024

A software development team may use dashboards showing alternative solutions, connected marketing strategies, user personas, customer problems, or frameworks prioritizing features based on data, user stories, and the existing product. Sustainable living plan 2010 to 2020: Summary of 10 years’ progress. 2020, May).

Sustainability 52

Sustainability Development Team Review Innovation 2024 52

MPUG

AUGUST 25, 2019

The 2010 version of Microsoft Project introduced some new functionality whose behavior has confused and confounded users with all degrees of experience, from absolute beginners to power users. Microsoft introduced this new functionality to fix a bug that had been present in the software since I first started using it many years ago.

2010 81

2010 2013 2016 2019 81

Herding Cats

MARCH 4, 2017

Software development project schedule estimation has long been a difficult problem. Reducing Estimation Uncertainty with Continuous Assessment: Tracking the “Cone of Uncertainty ” Pongtip Aroonvatanaporn, Chatchai Sinthop, Barry Boehm, ASE’10, September 20–24, 2010, Antwerp, Belgium. . "A For example for a recent paper abstract.

2010 28

2010 2007 Estimate Aerospace 28

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

ASE’10, September 20–24, 2010, Antwerp, Belgium. . [8] Software Engineering Economics”. Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Development Effort Estimation: Formal Models or Expert Judgment?” IEEE Software, March-April 2009, pp. Software Eng.,

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

ASE’10, September 20–24, 2010, Antwerp, Belgium. . [8] Software Engineering Economics”. Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Development Effort Estimation: Formal Models or Expert Judgment?” IEEE Software, March-April 2009, pp. Software Eng.,

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Wrike

AUGUST 14, 2020

Anderson is often credited as being the first to implement Kanban in software development in 2005. His book on Kanban , published in 2010, is still one of the most comprehensive resources out there for technology-focused projects. It wasn’t until the early 2000s that Kanban started to take root in project management.

Software Review 36

Software Review 2005 Technical Review SCRUM 36

EasyProjects

SEPTEMBER 24, 2019

For example, Microsoft, which began with one team in 2008, several teams in 2009, some 25 teams in 2010 in the Visual Studio group, then several hundred teams in the Developer Division in 2011, and then a commitment to take Agile across the whole organization around 2014. Scrum is used by software development teams.

Agile 41

Agile Technical Review Software Review Underperforming Technical Team 41

Herding Cats

FEBRUARY 4, 2017

ASE’10, September 20–24, 2010, Antwerp, Belgium. . [8] Software Engineering Economics”. Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Development Effort Estimation: Formal Models or Expert Judgment?” IEEE Software, March-April 2009, pp. Software Eng.,

Technical Review 28

Technical Review Estimate 2005 Software Review 28