Agile Modeling Design Workshop

Revision as of 06:00, 16 November 2008 by Clarman (talk | contribs)

Overview

2-5 days

In this case, a picture is definitely worth a thousand words:

Agile Modeling Pictures

For decades, I have coached and promoted agile design modeling -- using vast whiteboard spaces surrounding a development team, and then spending "2 hours to 2 days" each iteration "at the walls" to collaborate on design ideas, related to algorithms, objects, databases, UI sketches, and more. I encourage the use of simple visual modeling, using minimalistic "UML as sketch" where the emphasis is on creativity, flow, and communication with others. The theme is exploration and communication for design, not documentation.

Then, after a design workshop, the team can sit down at their tables, ideally surrounded by their sketches on the walls, and start implementing the product, inspired by the agile models on the walls.

Each iteration (or Sprint) the team may hold several design workshops, as they feel the need. I definitely encourage at least one workshop near the start of each iteration.


Methods of Education

primarily workshop coaching "at the walls"; some minor discussion, presentation, Q&A


Audience

This can only be for one product group. Attendees should include the cross-functional development team, the Scrum team composed of all areas of discipline (software, interaction design, domain expertise, database, architecture, business analysis, documentation, testing, ...) necessary for creating the product.


Level

This is an immersive workshop. No prior knowledge is absolutely required, but the experiences and knowledge will extend from introductory to intermediate or advanced. And, it the workshop is most effective for people who have met the prerequisites.


Prerequisites

There are not strict prerequisites. However, people who have attended any one of the follow courses will be better prepared to take full advantage of this workshop:


Objectives

This is not a course per se, but a product-specific (or 2 products maximum) workshop to create the release plan for a Scrum-based development release. Nevertheless, learning how to do agile release planning is an important complimentary goal, in addition to actually creating the plan. Thus, learning objectives include (but are not limited to):

  • agile estimating and planning
  • modeling with user stories
  • splitting large user stories
  • mind mapping
  • affinity clustering
  • Scrum Product Backlog creation
  • prioritization in Scrum
  • much more


Outline

  • Vision workshop
  • Requirements workshop
  • Effort estimation workshop
  • Value estimation workshop
  • Risk estimation workshop
  • Product (Release) Backlog shaping and prioritization


Maximum Participants

30


Environment - Room, Tools, Texts

Read this: Course Environment - Workshop Style1


Text and Notes