MP and Agile's events-activities and artefacts-information sets

NB - The mapping is from table 20.1, a blank entry means that MP and agile DON'T overlap on that item - I can't conceive of MP3 Deliver a Work-Package NOT involving User-Acceptance - Its clearly how normal p2 works for phased hand-overs - but that isn't exam friendly advice (or the manual is in error by omission)

• MP's Activities
  
  • MP1 [ Accept a Work Package [ 16.4.1 ]
  • MP2 [ Execute a Work Package [ 16.4.2 ]
  • MP3 [ Deliver a Work Package [ 16.4.3 ]
• Agile's Events
  
  • Release planning = MP1
  • Sprint planning = MP1
  • Daily Stand-up = MP2
  • Sprint review = MP3
  • Release review = MP3
  • Sprint demo =
  • User acceptance =
  • Release Demo =
  • Sprint retrospective =
  • Release retrospective =
• Artefacts
  
  • Release backlog = MP1
  • Release backlog status = MP3
  • Sprint backlog = MP1, MP3
  • Sprint backlog status = MP2
  • Burn charts = MP2
  • Information radiators = MP2
  • Shippable increment = MP3
  • Impediments = MP2
    • Daily impediments =
  • User story acceptance criteria =
  • Product backlog =
  • Outputs & decisions from retrospective & reviews =