Firstly, this post is about evaluating a decision that may save us a lot of money and time building an Atlassian plugin which people may not need, as well as work out what the pain points are which prevent Confluence and JIRA allowing you to effectively capture re-usable checklists such as best practices, how-tos, guidelines and procedures within your business.
We are building a startup (funded by the Government of Chile) called http://tallyfy.com
Tallyfy is a platform that will allow businesses to capture, use, analyse and improve best practices in the form of checklists. Effectively, the idea is to supercharge your workflow through the use of re-usable checklists for common things a business does, especially those processes which begin with "How to ..."
Before we invest a lot of time and resources building plugins for re-usable checklists (with analytics on Tallyfy) for Confluence and JIRA - would it be useful to you?
Do you think this plugin should be embeddable as a macro or use the new "Blueprints" feature of Confluence? Our idea was to simply create a new blueprint called "Checklist", which you can rename to "Best practice" if you like, to encourage correct usage of the feature. The business benefits of using, measuring and improving best practices are obvious - but I can elaborate if need be. They prevent avoidable mistakes and improve outcomes without any increase in skill.
Please note that this is NOT for task management, it's for re-usable checklists. We do intend to integrate into various task management plugins and apps though (if it's feasible) - linking what to do (tasks) with how to do it (Tallyfy checklists).
The idea is for us to integrate Tallyfy into Confluence through a plugin, and on the server-side - our SaaS will do all the real-time analytics and more. The part facing Confluence/JIRA will be lightweight (the user-facing end).
Your feedback is much appreciated. If you are very excited, there is a newsletter you can sign up to, at the bottom of http://tallyfy.com;-)
PS - one of our inspirations is the book "The Checklist Manifesto" by Dr. Gawande.
Great idea! I know lot people accomplish this use case by cloning subtasks in JIRA. See an example of this at http://ffeathers.wordpress.com/2011/04/12/jira-cloning-to-create-a-template-for-repeated-documentation-tasks/
If you do plan to build this I would do it as an Atlassian Connect add-on so that it can work in Atlassian OnDemand.
Thanks for the note, Bill. Hope to present this at a future Atlassian event (spoken at a couple in London already). I'll deep-dive into the cloning sub-tasks idea and see what's missing there. We have a whole analytics thing which is significant too as it enables averages to be seen for repeatable processes (enabling improvement).
Bill, one more question - which I can't seem to find an answer to anywhere. Is an Atlassian Connect add-on/plugin exclusively for cloud-based Atlassian instances?
If corporates/other customers had on-premise Confluence/JIRA installations, must I also make the "traditional" type of plugin?
Hi everyone - we need pilot clients for this and this needs to be led through customer needs. If you have a budget or use case that can help us achieve this, please let us know. We can be contacted via https://tallyfy.com
We also have an open API btw at https://api.tallyfy.com in case someone wants to do this.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot