International Institute for Learning

JULY 7, 2022

During the last two decades there has been the emergence of a number of software development methods as a response to the inefficiency of existing software development methods in rapidly changing environments (Highsmith, 2004). Agile Scrum Belgique Blog; [link]. ” Software Development 9(8): 28-32.

Innovation 59

Innovation Agile 2002 2001 59

Scrum.org

MAY 26, 2020

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. Both are Professional Scrum Trainers and Liberating Structures enthusiasts. Also, they are co-authors of the upcoming Zombie Scrum book .

Agile 100

Agile 2004 SCRUM 2010 100

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 223

2015 2014 2004 Influencer 223

Scrum.org

JANUARY 27, 2021

Audience: Scrum Masters , Leaders. In the complex world of Sales, Marketing, and Software Development, we also needed new ways of thinking that would power the same ideas from Toyota and Lean into the high variance world of complex cognitive work. Read: The Scrum Guide. The Scrum Guide. Subscribe to A Wee Dram!

2001 216

2001 Software Review Technical Review Underperforming Technical Team 216

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. So much that it is being used for other projects besides software development. Q1: Is Kanban better than scrum? The Scrum board is more methodical.

Software Review 81

Software Review Technical Review 2004 SCRUM 81

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.

2003 46

2003 2014 2015 2011 46

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

APRIL 4, 2019

Paul Chavas, Elsevier Academic Press, 2004. 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 in Software Development Projects , John McManus, Routledge, 2003.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

MAY 7, 2019

Effort Distribution to Estimate Cost in Small to Medium Software Development Project with Use Case Points,” Putu Linda Primandari and Sholiq, The Third Information Systems International Conference, Procedia Computer Science, 72, pp. 61, September 2004. How I Estimate Software Development Projects,” Alvin J.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

MAY 10, 2019

Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. 920, November 2004. 3 September 2004, Heiot Watt University, Association of Researchers in Construction Management , Vol. 255, April 2010. Talat Birgonul, and A. 85 1 Feb 2019. “An

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. Let's start with a critical understanding of the purpose of managing risk on software development projects. 920, November 2004. 255, April 2010. Kwak and J.

Risk Management 35

Risk Management Risk Technical Review 2002 35

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). 449-462, July 2004.

Estimate 64

Estimate 2006 2005 2012 64