2010 Innovation SCRUM Software Development 
Scrum.org
OCTOBER 19, 2022
And we share results from our own analyses based on actual data from stakeholders and Scrum teams that we collected through the Scrum Team Survey. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. We collected the data through our Scrum Team Survey. We worked with Prof.
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. Agile Project Management: Creating Innovative Products , Jim Highsmith, Addison Wesley, 2004.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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 .
Herding Cats
MAY 10, 2019
255, April 2010. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. 24, 2010. “A Project Risk Management: Lessons Learned from Software Development Environment,” Y. 920, November 2004. Kwak and J. Yamamoto, and K.
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 Kwak and J.
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.
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. Innovation and ideas for improvement should be promoted at all levels. Keep roles.
Expert insights. Personalized for you.
197 
Let's personalize your content