Thank you for this insightful video. I would like to connect with you for mentoring, new started my career and i really need guidance. do you have an email i could reach out to or a linkedin account. Thank you
I love the content... but your audio levels are so inconsistent between the two of you. One video Mike is really loud and then Kelly is faint... the next video it is swapped.
Thank ,really appreciate the cohesive presentation ,i enjoyed your delivery style and practicality, ill tested the HTML bug template,it works very well.keep up the great team work
On our board we split our columns up into process segments. These can be whatever you and your team want. The difference here is this. Approved = Work has been approved by the team to be worked on. However, it isn't committed to be worked on for this sprint. Committed = the team is committed to work on the items in that column in that sprint. A developer should take work from the committed and pull that item into the Development column. The flexibility of the boards allow you do to some very good tracking of progress. Let me know if this helps. -Mike
In my opinion, columns should always be flow of work. If you have a column that is "blocked", that means that a work item could go from the second column to the "blocked" column and then back to the third column. this messes up any metrics you want to track flow of work. Ultimately, you want work to go as fast as possible from left to right. If you have a blocked item, use tags and color code the card.
Hi there! Great video! Is there a way to configure a swim lane to be “awaiting response” and once a card is put in there, it will not could for the total time a card is active?
thank you for the video. I learned new things. Is there a way in ADO to prioritize the backlog by using a number other than the 1, 2, 3, 4 options in the Priority? If I have a rather small backlog and I want to go through the exercise of saying this is my most important item/issue/story/pbi down to the least important, is there a way to do it for ADO to display it that way? thank you
On the left navigation, Work items are those that are most active and what you worked on recently. Backlogs are hieratical (depending on the backlog level you're using) and all items in that team. - Mike
hello, about 8 min 20 seconds in Mike talks about splitting a Column and adding "doing" and "done". this is on a "main" Board. can the same function be performed in a Sprint Taskboard? we have a lot of Tasks and would like to split them in order to view more easily. similar question, can Swimlanes be added to a Sprint Taskboard.
By default, the sprint task board is already split into "To Do", "Doing", and "Done". The ability to add swim lanes to the Sprint board isn't available. -Mike
There's a custom extension that does this. marketplace.visualstudio.com/items?itemName=YodLabs.TagsManager2&targetId=4f5e75d9-a022-483d-894c-50e2d3262802&ExtHubManageList -Mike
I would like my tasks to have a specific color when they are in a specific column. Is that possible? I have tryed with Field = "Board Column" and Value = "Name of Column". It dosn't work.
It is possible. Not sure why yours isn't working. Would it be better to use Tags to specify different colors or some other property. One approach is to use color sparingly to draw attention to items that need attention. The kanban board is a great visual management tool for ease of status update. -Mike
ADO has such a terrible User Interface that any alleged efficiency benefit is lost due to each lay user wasting half a day monthly entering and managing User Stories. Every little thing associated with is cumbersome, counter-intuitivive. Users can't tell where content is vs control buttons. Most of the icons don't make sense. The documentation is inadequate and is not aimed at tje most populous class of users: Worker Bees who ONLY deal with User Stories 1 day per Sprint. Of course anyone can overcome clunky software interfaces if spending all day, every day using the software. But, most lay users don't. Development Managers who think that ADO provides value aren't noticing how productivity evaporates on the first and last days of a Sprint. Although it is possible to accomplish these tasks un 10 minutes, no lay user does. They spend hours.
