Traditional Role

  • Do work assigned (push vs. pull)

  • Help the team coordinate and collaborate (weekly, monthly)

Agile Modifications to the Role

  • Individuals select (pull) their own work items from the prioritized buffer column (ready, backlog or "done" from prior step).

  • Although an individual fulfills one or more roles on a project team, that does not imply that the person is constrained to doing only specific types of work.

  • Members coordinate and synchronize with the team daily at the daily standup meeting and impromptu discussions between individuals.

  • The team member helps keep the iteration cadence. All team members are required to attend.

  • Team members move their work item cards BEFORE the daily standup. Team members don’t spend time verbally providing status, instead the Kanban board visually provides the status to all so the team can collectively address traffic jams, bottlenecks and constraints on the board.

  • Team members are prepared to pull cards and commit to what they will do today.

  • Team members tell the team what is impeding their work.

  • Team members make working courseware functionality available as early as possible.

  • Team members test their own work items before calling it "done" to ensure it works as expected. The goal is to find and fix defects. Test to the risk. The riskier something is, the more it needs to be reviewed and tested.

  • Team members continuously integrate their components into the courseware build using the courseware authoring software.

  • Everyone commits to the work. The team commits to accomplishing the iteration goal by the end of the two-week iteration. Individuals commit to the work items they pull and add their avatar to the work item card to signal ownership to others.

  • Everyone contributes.

  • No one stays only to their specialty.


Line By Line

Here a Little, There a Little, Layer by Layer.

Back to Overview