Hacker News Reader

Comment by simonswords82 | Hacker News Reader

We use Microsoft Azure Dev Ops Boards. It's okay for the engineers but pretty crap outside of that at a project/business level. So much so that we revert back to Trello almost as a layer above dev ops but that duplicates the information we store about sprints/cards etc. Not ideal

Would love to hear from anybody who has found a way to make Microsoft dev ops sing at a project management level!

View on HN

We also use Azure DevOps. Where I work, developers, testers, designers, product owners, product managers and so on all use it without too many issues. It helps that you can create a hierarchy, with epics and features being more high-level, and user stories and tasks being more low-level. This allows people in different roles to work at a level of abstraction that works for them.

That said, we also maintain high-level roadmaps in ProductPlan, which we've found to be more suitable for non-tech stakeholders, since it lets you quite easily see where projects sit on a timeline and the dependencies involved.

We do a similar thing. Engineering tracking is done through AZDO, but roadmap management is done in another tool with some sort of integration between the two.

Would love to hear more about this - how do you integrate the two?

Our Product Team use Devops, particular the "Features" part which makes it easier to organise at a high level but also you can easily link to other PBIs created to implement those features.

My experience is really related to people's willingness to try things out. Most objections I have had to using these tools relate to technophobes or simply people who don't like it and won't use it!

This is a horrible tool, and it's highly likely that everyone actually hates it but just doesn't want to say anything.

Glad to hear it's not just some members of team who struggle with it!

What do you prefer?

I think for me Trello is the only tool that makes it hard for managers to turn into a hellscape.

Reply on news.ycombinator.com