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

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.
The definition of done is an agreed upon list of the activities deemed necessary to get a product increment, usually represented by a user story, to a done state by the end of a sprint.
The scrum master is the team role responsible for ensuring the team lives agile values and principles and follows the processes and practices that the team agreed they would use.
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.
Usability testing is an empirical, exploratory technique to answer questions such as "how would an end user respond to our software under realistic conditions?"

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.

Privacy Preference Center

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.