When Do you plan to cover ‘Test Plans”. I would ‘vote’ for ‘test plans’ overview and than more detailed tips and best practices next. The deeper dive into estimation mention in backlog video is also of high interest.
Question: I have opted to use T-shirt size, but this does not save. I assume that this is because the ST field is set to a decimal and therefore cannot accept text. Is this something that can be updated to accept free text ( i.e. how does this effect velocity) or must a new field be created ? IF a new field is created and set on estimations, is there a way to have each estimation look at a separate field or does one rule, rule them all ? I ask as i want to do an offline t-shit size across the whole team BEFORE doign actual SP's on pods within the team Thanks
Thanks Kelly & Mike for the series. Couple new extensions for me i want to try based on this. Thanks Want to Echo use of retrospective by dev Labs - we use regularly - very helpful. Not mentioned here, but our team uses Storyline by Eric B for sp voting remotely. Also maybe overlooked, but i could not live with out Azure Dev Ops Open in Excel by Microsoft Dev Labs. If ever a ‘must have’ extension this is one.
Thanks Kelly and Mike for the great video! I was wondering, is there a way to link two separate DevOps boards? For example, if I move a feature in one board the duplicate feature moves in the other board?
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.
Thanks Kelly and Mike!, I found this video really useful and I already installed some of your favorites extensions!.
Really great video! Thanks for mentioning 'Query Based Boards' 🙂
Kr
Edward
When Do you plan to cover ‘Test Plans”.
I would ‘vote’ for ‘test plans’ overview and than more detailed tips and best practices next.
The deeper dive into estimation mention in backlog video is also of high interest.
Question: I have opted to use T-shirt size, but this does not save. I assume that this is because the ST field is set to a decimal and therefore cannot accept text. Is this something that can be updated to accept free text ( i.e. how does this effect velocity) or must a new field be created ? IF a new field is created and set on estimations, is there a way to have each estimation look at a separate field or does one rule, rule them all ?
I ask as i want to do an offline t-shit size across the whole team BEFORE doign actual SP's on pods within the team
Thanks
Thanks Kelly & Mike for the series.
Couple new extensions for me i want to try based on this. Thanks
Want to Echo use of retrospective by dev Labs - we use regularly - very helpful.
Not mentioned here, but our team uses Storyline by Eric B for sp voting remotely.
Also maybe overlooked, but i could not live with out Azure Dev Ops Open in Excel by Microsoft Dev Labs. If ever a ‘must have’ extension this is one.
Hi Kelly & Mike.... Could you please organize a session only on Agile Project Management using Devops.... For a Non Technical Project Manager.
Thanks Kelly and Mike for the great video! I was wondering, is there a way to link two separate DevOps boards? For example, if I move a feature in one board the duplicate feature moves in the other board?
Did you get an answer to this question?
thanks! i like some of your videos! but sometimes your audios are quite a problem :s
Great video but the sound is terrible. Both of you need to buy some good microphones. Kelly's microphone is particularly bad.
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.