How’s that sprint going? ZenHub reporting and GitHub data will tell you
My experience has been that no one needs a burndown chart to know how a project is going, and, to the extent that you do, it usually points to some mismanagement and an attempt to fix it through intensifying project management rigor.  Especially with early stage startups, where the requirements are changing rapidly and throughout the project, I think this stuff represents very real overhead that&#x27;s just not really that useful.  In larger companies, where stuff like this is typically used as reporting up a chain, it can be slightly more useful to get a holistic view of the organization, but again, I&#x27;m just not sure it&#x27;s worth the effort, and I really question resting a significant amount of decision making power on this over qualitative data.<p>To be clear: I&#x27;m not throwing all project management methodology to the wind, but this promises to give you a fancy chart that will &quot;identify bottlenecks in your development process&quot; and I&#x27;m sorry if you need a graph to know where those are I think there are probably larger problems in your organization.  Identifying bottlenecks is easy, fixing them usually involves much higher level management functions like recruiting and training.