This was a great overview and clear explanation of when and why to use ADO! I'd really love to see more about how individual team members manage the user stories assigned to them, how tasks are used and managed, etc. For example, what are my interaction points with ADO throughout the day as I work on a particular user story? Am i creating and closing tasks as I see fit, am I looking at the whole backlog and navigating just to my items? Would love to see your thoughts on day-to-day use of ADO.
Hi Dani, What part of Azure would you suggest works with this to form the documentation, like a PRD or PRFAQ etc. The classic Confluence and Jira solution, lets me do all my Product documentation in Confluence, then I can pull stories from Jira into confluence to make a more digestible presentation of stories for the Business stakeholders to review. They won't be reading Kanbans and Backlog lists. So how would I best approach this with Azure?
Hi, not sure as I don't know Jira nor Confluence well enough. And from reading what you are saying... I don't think that you can easily do that in Azure DevOps.
Hi Dani, thanks for the video, very informative indeed. I wonder if you created the image on ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-hX9jabZBxm0.html or got it from the docs, I find AzureDevOps could be do a better job on explaining its features. More intuitive UI and direct links to video and a more intuitive documentation would also be welcome. Anyways, thanks again for the video.