3 ms·

As long as you use Jira and Confluence to track what you are doing and make handy reference notes, they work super good. About showing burn down chats: usually

As long as you use Jira and Confluence to track what you are doing and make handy reference notes, they work super good. About showing burn down chats: usually they are shown a few times in early stages of the project, but don't get any attention anymore once they start showing unwanted or erratic results. Also story points estimations/tracking (as opposed to time in real world units) : never saw it work in practice. Whoever says software/hardware project time schedules are 'under control' or 'predictable' is probably joking.

Macha 4y ago
I would argue that the performance of Jira being what it is along makes it pretty unsuitable for just taking reference notes. Our onprem hosted instance is pretty slow, which you might blame on server provisioning, except last time I used Jira cloud it was even worse with an empty instance (compared to our at least multiple million tickets instance)
- nuancebydefault 4y ago
  Well Confluence is for the handy notes, which can grow into quality documents if you have them reviewed and updated. Personally never experienced performance issues.
majormajor 4y ago
> About showing burn down chats: usually they are shown a few times in early stages of the project, but don't get any attention anymore once they start showing unwanted or erratic results. If your management can't understand these charts - including when you get results you don't want - I think your management is failing. E.g. if you don't realize "whoa there's a lot more ambiguity here than we expected and it's causing big delay" until the project goes sideways trying to find clarity, then you missed something big in your earlier planning and estimation. And whether or not it was important to spend the time to try to get a more accurate estimate vs just start building should be a business-requirement and project-specific decision, but it should be a conscious one.

Macha 4y ago

I would argue that the performance of Jira being what it is along makes it pretty unsuitable for just taking reference notes. Our onprem hosted instance is pretty slow, which you might blame on server provisioning, except last time I used Jira cloud it was even worse with an empty instance (compared to our at least multiple million tickets instance)

nuancebydefault 4y ago
Well Confluence is for the handy notes, which can grow into quality documents if you have them reviewed and updated. Personally never experienced performance issues.

majormajor 4y ago

> About showing burn down chats: usually they are shown a few times in early stages of the project, but don't get any attention anymore once they start showing unwanted or erratic results. If your management can't understand these charts - including when you get results you don't want - I think your management is failing. E.g. if you don't realize "whoa there's a lot more ambiguity here than we expected and it's causing big delay" until the project goes sideways trying to find clarity, then you missed something big in your earlier planning and estimation. And whether or not it was important to spend the time to try to get a more accurate estimate vs just start building should be a business-requirement and project-specific decision, but it should be a conscious one.