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

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. LEARN MORE >

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

Test-driven development (TDD) is a style of programming where coding, testing, and design are tightly interwoven. Benefits include reduction in defect rates.
The daily meeting is one of the most commonly practiced Agile techniques and presents opportunity for a team to get together on a regular basis to coordinate their activities.
The team meets regularly to reflect on the most significant events that occurred since the previous such meeting, and identify opportunities for improvement.
The Given-When-Then formula is a template intended to guide the writing of acceptance tests for a User Story: (Given) some context, (When) some action is carried out, (Then) a particular set of observable consequences should obtain.
Agile teams generally prefer to express estimates in units other than the time-honored "man-hours." Possibly the most widespread unit is "story points."
Version control is not merely "good practice" but an enabler of a number of Agile practices, such as continuous integration

Help us keep the definitions updated

Ready to join Agile Alliance?

Unlock members-only access to online learning sessions, Agile resources, annual conference discounts, and more! And when you join, you’ll be supporting our member initiatives, regional events, and global community groups.

IMPORTANT: We have transitioned to a new membership platform. If you have not already done so, you will need to SET UP AN ACCOUNT on the new platform to establish your user profile. Your previous login credentials will not work until you do this set up.

When you see the login screen, choose “Set up Account” and follow the prompts to create your new account. You can choose to log in using your social credentials for either Google or Linkedin (recommended), or you can set up your account using an email address.