![]() ![]() For example, it might become clear that a task needs tests before it can be completed, so there might be a column for that.The task board is another buffer in the whole “plan and execute work” process, facilitating conversation around the state of work and impediments.What task boards tell us, and how they are useful.The board is often updated once daily, when the team meets, but can also be continuously updated as long as doing so benefits others.You could have a row for expedited needs ("Urgent").Phab can't really do that, but for the sake of completeness. Sometimes there are rows in addition to columns (rather than one row and several columns).What do we have to do? What is impeding us from doing it? What level of granularity is required to clarify efficiently? Regardless, most teams traditionally adapt the board to the process components they want to call out (including "Testing" or "Needs Review" or "Blocked" etc).Sorta like, "if you have A, you must have B, but not necessarily C." "In Progress" is a commonly cited 3rd, intermediary column, but technically it's not necessary."To Do" and "Done" are the old-school columns.If a board isn't working for a team, it's worth considering if that the team is doing is actually what isn't working.The board should be built and used collectively.The board should clarify what information the team wants to transmit.The board should represent the team's process of work. ![]() The board is a mirror of the team's process, work, discussion, etc, aside from that which typically happens on a backlog instead.This obviously relies on the backlog being in good enough shape.You can be granular with ordering in the task board, but it's nuanced and I dunno that there is a standard beyond "top thing first.".The idea is that once a task is on the task board (and out of the backlog), it's relevance is inherent, and it's about "how do we get this finished" and not "why are we doing this, and in this order.".The task board focuses on "state" while the backlog focuses on "type" or "category" or "priority" etc.Usually, this includes the team members with whom you collaborate.It’s generally easier to do that in a place separate from the pile of future work (the backlog). That means it is also a place where there is a narrative about the work, and you don't have to read your email or even leave your to-do list, to hear that narrative. It’s a place where you can visualize the scope of your current work, your focus.The black list-items are subjects, the sub list-items are sorta sectional TL DRs, and anything deeper is detail. Exhaus ting maybe, but I'll let you decide. :) This is by no means an exhaustive descriptor. I've tried to limit this email to the board's "traditional" purpose, some different philosophies, as well as what I observe with this team. It does not necessarily show why you are doing something, or how, but in many versions does. Most simply put, a task board is an information radiator, and shows what you have committed to, what you are doing, who is doing what, etc, to the team as well as outsiders to the team. The scope of "what is the sprintboard for" is interdependent with other process things like "who owns the backlog" and "what is X person's role," so it's something that can take us a lot of different directions. It is posted here because it has often been shared privately and the info is useful to have in a public space. If you notice anything that should be precisely cited with a known source, please feel free to do so. Note: this was originally written for a single Wikimedia team and a small audience, with a lot of sourcing from all over the internet, so it's likely lifted entire phrases or sentences without precise attribution. Feel free to update this page as needed, or use the discussion page to propose major changes. It expresses the opinions and ideas of some users, but may not have wide support. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |