Very good video! I have a question, Where registred the procesos map for after wirte historias, for example, if in sprint 1 I want to map a sales process and then create stories, where would I record the tasks before creating the stories? Thank you
Close but a few things wrong with this. 1) testing is built into devops so hou dont have test tasks. You use testing. 2) tech stories make no sense. They are all user stories. Ie as an infrastructure engineer i need a sql database setting up. 3) dont mix points and time. Just do one. Commit to doing say 40 points in a spint. If you only do 26 then next sprint only commit to 26. Dont estimate time, feel free to track how long it actually took though. Only estimate a story after all tasks are planned. Dont resize a story EVER. Learn from it and resize as a team correctly in the future. Dont over point or under point. Make use of epics, and features, learn this properly and you will do ok.
The best video on UA-cam for the Azure DevOps.Thank you
Thank you
so true
The best video on azure dev ops sprint planning. Thank you.
Thanks for your kind words
I am a UX designer my company wanted to me handle a PO role also. This helped a lot liked & subscribed
Thank you
Thanks for your time; helped a lot!
You are welcome
Superb explanation
Very good video! I have a question, Where registred the procesos map for after wirte historias, for example, if in sprint 1 I want to map a sales process and then create stories, where would I record the tasks before creating the stories? Thank you
Well explained. A really helpful video.
Thank you
thank you for your effor. very helpful
You are welcome
nicely explained, Thanks!
You are welcome
Can I create multiple Sprints based 1 epic?
Yes you can.
Hi! Can I request you to make tutorials on QA roles in this Azure DevOps? Thank you in advance!
Ok, thanks for your feedback
Close but a few things wrong with this. 1) testing is built into devops so hou dont have test tasks. You use testing. 2) tech stories make no sense. They are all user stories. Ie as an infrastructure engineer i need a sql database setting up. 3) dont mix points and time. Just do one. Commit to doing say 40 points in a spint. If you only do 26 then next sprint only commit to 26. Dont estimate time, feel free to track how long it actually took though. Only estimate a story after all tasks are planned. Dont resize a story EVER. Learn from it and resize as a team correctly in the future. Dont over point or under point. Make use of epics, and features, learn this properly and you will do ok.