Scrum.org
DECEMBER 18, 2020
In the end, the sources I used for describing the evolutions of the definition of Scrum are: The paper “SCRUM Software Development Process” by Ken Schwaber (1995, 1996). The book “Agile Software Development with Scrum” by Ken Schwaber and Mike Beedle (2002). The book “The Enterprise and Scrum” by Ken Schwaber (2007).
Scrum.org
AUGUST 1, 2022
Butchibabu and her colleagues (2016) performed an experiment with 13 teams. In those situations where team members frequently have to work with new members, it is not surprising that much more effort will need to be made to continuously develop, refresh and refine work agreements and shared mental models. References. Butchibabu, A.,
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
The IIL Blog
MAY 17, 2023
My Keynote Presentation is about the development of project management and project managers in the Bosch Group. I will focus on two selectively chosen business units that have already gone through the agile transformation: ETAS (Bosch’s Software Development Subsidiary) and Bosch Power Tools. They have a sales revenue of 5.9
Gunther Verheyen
DECEMBER 17, 2020
For every source I have described the same three topics to show what Scrum consisted of at the time (regardless the different terms used), what the ‘definition’ of Scrum was at the time: Roles, responsibilities, accountabilities Controls, deliverables, artifacts Phases, meetings, time-boxes, events.
Gunther Verheyen
FEBRUARY 26, 2024
In 2011 I obtained my license as a Professional Scrum Trainer for Scrum.org from Ken Schwaber (co-creator of Scrum). From 2013-2016 I maintained the official “Professional Scrum” series of Scrum.org meanwhile training candidate-PSTs and shepherding the global community of Professional Scrum Trainers and coaches.
Scrum.org
OCTOBER 19, 2022
Several empirical studies have indeed found that teams with a frequent delivery strategy are more likely to deliver successful project outcomes and satisfy stakeholders than teams that do not ( Chow & Cao, 2008 , Jørgensen, 2016 ). Hoda, Stuart & Marshall (2011) interviewed 30 Agile practitioners over a period of 3 years. Cruzes, D.
Herding Cats
MAY 10, 2019
IEEE Transactions on Software Engineering , Vol. 5, September/October 2011. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. 2128, International Technical Paper , 2016. 3, March 2002. 255, April 2010. 920, November 2004.
Expert insights. Personalized for you.
229 
Let's personalize your content