28.2SEMay 2
A Lightweight Scrum Sprint Simulation to Help Learners Traverse the Empirical Process Control Threshold ConceptEduardo Miranda, Torgeir Dingsøyr, Pritam Chita
Empirical process control, a way of managing work based on the observation of the successes or misfortunes of earlier activities, is a key process in Scrum and other agile development frameworks. In this experience report, we present a lightweight, scalable, free and customizable sprint simulation activity designed to teach students how to empirically control a Scrum project by engaging in the presentation and interpretation of work status information, task selection and resource allocations in a single teaching session. We reflect on our experience using the simulation as an active learning complement to direct instruction in two master level courses at two different universities and in the training of teaching assistants at a third institution, and abductively establish its effectiveness by mapping student comments to the teaching practices in the threshold concepts framework.
25.5SEMar 25
Bridging the Gap Between Agility and PlanningEduardo Miranda
Milestone Driven Agile Execution is a hybrid management framework where the empirical control component of agile development is retained but the prioritization of the backlog is done according to a macro or strategic (milestone) plan that drives the execution of the project. MDAX is method agnostic, in the sense that the development approach is not embedded in the execution mechanism but in the plan that drives it. This allows organizations using it to choose the development approach that suites them most,
26.6SEApr 23
Documentless Assessments Using Nominal Group InterviewsEduardo Miranda
This paper describes a group interview technique designed to support documentless process assessments while promoting at the same time collaboration among assessment participants. The method was successfully used in one consulting assignment where it got previously discording participants, talking to each other and agreeing on the issues. The technique borrows from agile software development the concept of user stories to cast CMMIs specific practices in concrete terms and the Planning Poker technique, instead of document reviews and audit like interviews, for fact finding and corroboration.