Feel free to use the role-plays linked below!  Here's how:

Eight students form a "company" that will develop a new technology in successive "sprints."  The game should be played quickly, to mimic some of the pressures of a real Agile work environment (about 45 minutes is enough for all four sprints).  As the students make choices and discuss them, each new "sprint" reveals new information about the tech and new choices to make.  And as each sprint moves along, other students comment on the discussion as "stakeholders" -- either members of the board of the company, tech writers for a magazine like Wired, or end users of the product under development.

Before the role-play occurs, the eight students playing the "characters" on the development team should receive the background information on the "company" they'll be playing, along with all the descriptions of each of the other characters.  Each one should also receive their own -- not others' -- "private information" about their hidden motives.  The new information and choices embedded in the description for each sprint should be withheld, to be revealed only in the course of play.