4 ms·
I find Azure Devops (VSTS) to be just as poorly designed for this purpose of macro design. Work isn't a linear process.
by catchmeifyoucan 8y ago
I find Azure Devops (VSTS) to be just as poorly designed for this purpose of macro design. Work isn't a linear process.
- alkonaut 8y agoVSTS and Jira are two implementations of the same thing really. They are the two large enterprisey issue management suites. They are "the worst except for all the others". If you really are a huge enterprisey team that has many levels of visibility for various management levels and stakeholders, as well as large distributed teams working with different schedules and modules, then github tags or post-it notes eventually won't cut it. They are nice and streamlined for a while, but then someone will ask for a weekly report of X or a website showing progress Y and a corollary to my main argument is that someone is always to oblige with the request even though the correct answer may be "no! Let us just use streamlined tools and just make smaller independent teams!". And in the end if you start off with post-its, the github issue tracker or some lightweight issue management system you'll end up according to this theorem: Every software project management system in a large enterprise environment that isn't already a large enterprise one (like Jira), will eventually become an ad-hoc, informally-specified implementation of Jira.