Everyday Guidebooks
Cover of Azure DevOps Work Items That Work

Cybersecurity & IT

Azure DevOps Work Items That Work

A Practical Guide to Backlogs, Acceptance Criteria, Dependencies, and Iteration Reviews

by Todd Michael

Available now

Your backlog should help your team deliver—not become another project to manage.

Azure DevOps Work Items That Work is an independent, practical guide to organizing work in azure devops so everyone can see what matters, what is ready, and what is getting in the way. Follow one team through an iteration as it turns a messy request into a manageable hierarchy, writes acceptance criteria, identifies dependencies, and makes sensible priority decisions.

Inside, you’ll learn how to choose the right level of detail, split oversized work, link related items, prepare for iteration planning, and use reviews to improve the next cycle. Worked examples, checklists, and discussion prompts help you adapt the practices without adopting unnecessary ceremony.

Whether you are new to Azure Boards or preparing for a role-based IT certification, this book connects work-item concepts to the everyday decisions teams make. It is not an official Microsoft publication or an exam-preparation guide.

Contents
  1. 1. A Backlog That Helps the Team
  2. 2. Meet the Work Items
  3. 3. Build a Hierarchy with a Purpose
  4. 4. Capture Requests Without Committing Too Soon
  5. 5. Write Acceptance Criteria People Can Use
  6. Start with the outcome
  7. Describe behavior, not activity
  8. Choose a form the team can read
  9. Make boundaries and exceptions visible
  10. Separate item criteria from the definition of done
  11. Find the right amount of detail
  12. Use examples to expose disagreement
  13. Record the agreement in Azure Boards
  14. Review the criteria together
  15. From written conditions to a shared result
  16. 6. Split Work Without Losing the Outcome
  17. 7. Make Dependencies Visible
  18. 8. Refine Just Enough
  19. 9. Prioritize the Backlog
  20. 10. Plan a Realistic Iteration
  21. 11. Keep Work Moving During the Iteration
  22. 12. Review Results and Return Learning to the Backlog
  23. Start with the Outcome, Not the Board
  24. Compare the Result with the Agreed Criteria
  25. Show Unfinished Work Honestly
  26. Invite Feedback Without Promising the Backlog
  27. Decide Where Each Observation Belongs
  28. Keep Decisions Close to the Work
  29. Revisit Unfinished Work Before Planning Again
  30. Reorder with the New Information
  31. Finish with a Clear Next Step
  32. 13. Find and Fix Backlog Decay
  33. 14. Put the System to Work
  34. Other Books by Todd Michael

Read a sample: 1. A Backlog That Helps the Team

On Monday morning, the team receives a message from a customer support manager:

> “Customers keep asking where their requests are. We need a dashboard with notifications, better reporting, and an export. Can this be ready for the next release? Also, please make sure managers can see everything.”

The message is familiar in the way that makes a team uneasy. It names a real frustration, several possible solutions, an implied deadline, and an access requirement that could mean more than one thing. It does not say which customers are affected, what information they need, or what “everything” includes.

A developer could create four tasks and begin building. A project manager could ask for a complete specification before allowing the request onto the backlog. Neither response is necessary. The team needs a place to capture the request, a way to make the important questions visible, and a process for deciding what deserves attention first.

That is the job of a useful backlog.

An effective backlog is not simply a list of tasks waiting to be assigned. It is a shared decision-making tool. It helps the team understand possible work, compare its importance, prepare the most valuable items, and learn from what has been completed. Azure DevOps Boards can support that work by keeping descriptions, relationships, ownership, status, and discussion close to the items they concern. The quality of the backlog, however, depends on the conversations and decisions behind those records.

This chapter establishes a practical standard for the rest of the book: maintain enough information to make good decisions, but not so much that maintaining the system becomes a second project.

A backlog gives a team a current view of work it may do. Some entries will be well understood and close to implementation. Others will be early ideas that need investigation. A few may eventually be declined or become irrelevant. Their presence in the backlog means they have been captured for consideration; it does not automatically mean they have been approved, scheduled, or promised.

That distinction protects both the team and its stakeholders. If every suggestion is treated as a commitment, the backlog becomes an accumulation of promises nobody has compared against available capacity. If the team refuses to record anything until every detail is settled, useful requests can disappear into email threads and meeting notes.

A useful backlog supports several connected activities.

First, it preserves the reason for work. A title such as “Build dashboard” suggests a solution, but it does not explain the problem. If the team knows that customers cannot tell whether a service request has been received or is being handled, it can evaluate a dashboard alongside other ways to improve that experience.

Second, it makes choices visible. A team usually has more possible work than it can do immediately. An ordered backlog helps people see what is most important now and gives them a basis for discussing why one item is ahead of another. The order is a decision, not a permanent property of an item. New information can change it.

Third, it supports preparation. An item near the top of the backlog should have enough clarity for an informed conversation about doing the work. An idea that may not be considered for months does not need the same level of detail today. Preparing everything equally would consume time that could be spent delivering or learning.

Fourth, it connects work without hiding the outcome. A larger goal may contain several deliverable pieces, each of which may involve implementation tasks. Those relationships can help people understand how daily work contributes to a broader result. They can also become an elaborate filing system if each new layer exists only because a template allows it.

Finally, a useful backlog retains learning. When the team discovers that an assumption was wrong, a dependency will take longer than expected, or a stakeholder needs a different result, the affected work items should reflect the change. The backlog is not a transcript of every conversation. It is a place to retain information that will help someone make the next decision or perform the next piece of work.

A simple test is to ask what question an item or field helps answer. If nobody can explain its purpose, the team may be maintaining information out of habit rather than need.

Different people approach a backlog with different questions. A product owner may want to know which outcome matters most. A tester may need to understand how to tell whether an item works. A developer may be looking for an unresolved technical constraint. A support representative may need confidence that a customer problem has been understood.

The backlog does not have to answer every question in full. It should make important answers discoverable and expose important gaps.

For example, an item might say that customers need to see the current status of a support request. It may also note that the source of reliable status information is not yet confirmed. That note does not solve the problem, but it prevents the team from mistaking an assumption for an established fact. The next useful action might be a conversation with the group that owns the support system.

A shared backlog is also different from a collection of personal to-do lists. Individuals still need to organize their work, but the team backlog should show the work and decisions that affect the shared outcome. “Ask Morgan about…

More Cybersecurity & IT

Cover of The White Hat Bible, Volume 1The White Hat Bible, Volume 1Available nowCover of The White Hat Bible, Volume 2The White Hat Bible, Volume 2Available nowCover of The White Hat Bible, Volume 3The White Hat Bible, Volume 3Available nowCover of The White Hat Bible, Volume 4The White Hat Bible, Volume 4Available nowThe White Hat Bible, Volume 5Available nowCover of The White Hat Pocket GuideThe White Hat Pocket GuideAvailable now

About Todd Michael

Todd Michael is an American author and the founder of ToddMichael.tv. He writes practical, plain-English books on money, health, preparedness, technology, games, humor and more.

About the author Todd Michael · Todd Michael’s author site

Part of the ToddMichael.tv network.