Architects of Interactive Learning

Key Design Process Principles

Agile Software Development Principles (The Agile Manifesto): Customer Collaboration, Individuals and Interaction, Responding to Change, Working Software over Extensive Documentation

Active Management of Scope

MoSCoW Rules (DSDM, 1997): A way of prioritizing user scenarios and feature to ensure that the right features are implemented first.

Team Learning: The team continually learns by sequencing development and testing so that end users are providing as much useful feedback as possible, as early as possible, and throughout the product development effort

“Deciding As Late As Possible”: Also known as “keeping the door open as long as possible”, this amounts to making decisions at the “last responsible moment”, the moment at which failing to decide eliminates a significant option (Lean Software Development, 2003). This has the dual benefits of allowing a team to minimize irreversible actions and maximize the impact of team learning.