Agile Glossary

Sign Up For Tasks

What is Sign Up For Tasks?

Members of an Agile development team normally choose which tasks to work on, rather than being assigned work by a manager.

Their choice may be negotiated in discussion with other team members. These discussions typically take place while standing before the task board, often during the daily meeting.

Signing up for a task is usually represented by an annotation on the index card or sticky note that stands for the task in question. Some teams use smaller stickies, photo portraits, or “avatars” temporarily attached to the task.

Common Pitfalls

Although seldom highlighted as a full-fledged Agile practice, the allocation of tasks based on self-selection rather than an assignment by a third party (whether a project manager, lead developer, or another role) appears to be an important, possibly most essential, feature of Agile work.

While transitioning to Agile, some teams may temporarily retain a project management role, including the authority to assign tasks to other team members. This is however incompatible in the long run with most other practices. Failing to explicitly address this area may therefore jeopardize such transitions.

Origins

  • 1998: the earliest writing on Extreme Programming mentions “tasks assigned” vs “tasks self-chosen” as one of the salient differences between the “old way” and the Extreme Way.

See more at:

http://guide.agilealliance.org/guide/sign-up-for-tasks.html#sthash.frkUagOG.dpuf

Add to Bookmarks Remove Bookmark
Add to Bookmarks Remove from Bookmarks
Add to Bookmarks Remove from Bookmarks

Thank you to our Annual Partners​

Join us today!

Agile Alliance offers many online and in-person events and workshops for our members. If you’re not currently a member, you can join now to take advantage of our many members-only resources and programs.

Get the latest Agile news!

  • This field is for validation purposes and should be left unchanged.

By subscribing, you acknowledge the Agile Alliance Privacy Policy, and agree to receive our emails.

Additional Agile Glossary Terms

An acceptance test is a formal description of the behavior of a software product, generally expressed as an example or a usage scenario. A number of different notations and approaches have been proposed for such examples or scenarios.
Test-driven development (TDD) is a style of programming where coding, testing, and design are tightly interwoven. Benefits include reduction in defect rates.
The team meets regularly to reflect on the most significant events that occurred since the previous such meeting, and identify opportunities for improvement.
A product backlog is a list of the new features, changes to existing features, bug fixes, infrastructure changes or other activities that a team may deliver in order to achieve a specific outcome.
An acceptance test is a formal description of the behavior of a software product, generally expressed as an example or a usage scenario. A number of different notations and approaches have been proposed for such examples or scenarios.
Test-driven development (TDD) is a style of programming where coding, testing, and design are tightly interwoven. Benefits include reduction in defect rates.
The team meets regularly to reflect on the most significant events that occurred since the previous such meeting, and identify opportunities for improvement.

Help us keep the definitions updated

Discover the many benefits of membership

Your membership enables Agile Alliance to offer a wealth of first-rate resources, present renowned international events, support global community groups, and more — all geared toward helping Agile practitioners reach their full potential and deliver innovative, Agile solutions.

Not yet a member? Sign up now