In this post you will know what is Confluence. JIRA and Confluence are two separate products from Atlassian. Put simply, JIRA is an open, fully customization platform for organizing teams around tasks/projects/initiatives. Task dependencies, resource accesses, permissions, hierarchies, etc can all be set up. PMs and Agile leaders can then watch software backlog planning, release planning, and overall progress. The framework of JIRA can also be used for business teams, and isn’t boxed into just software development.
Confluence, put simply, is a knowledge base, or wiki, that stores and organizes all of your information assets around the projects you’re doing in JIRA (like, product requirements), or general things like meeting minutes, marketing assets, design documents, how-to’s etc. Confluence integrates with JIRA easily, so these assets become an integrated piece so teams can create, collaborate and update on these assets seamlessly.
Confluence's features have moved a bit beyond dev in many orgs - plenty of biz teams now use it to plan project requirements and gather feedback along the way. Some examples in product: lots of formatting options and the ability to include rich content (images, videos, code, Word docs, etc.) for crafting 'single source of truth' project proposals, timelines, meeting notes and status reports.
More and more IT teams are adopting Confluence too - to centralize technical documentation, policy procedure and knowledge base articles to better support and service internal 'customers'. Prime example: building a self-service, searchable knowledge base of Confluence articles authored by various team members and integrating that with incident management or IT service desk tools such as JIRA Service Desk.
No comments:
Post a Comment