Confluence

Confluence

Business Tools / Collaboration / Project Management

Decision at Herman Miller about GitHub, Confluence, Jira

Avatar of davidritsema
Frontend Architect at Herman Miller ·

We knew how we wanted to build our Design System, now it was time to choose the tools to get us there. The essence of Scrum is a small team of people. The team is highly flexible and adaptive. Perfect, so we'll work in 2 week sprints where each sprint can be a mix of new R&D stories, a presentation of decisions made, and showcasing key development milestones.

We are also able to run content stories in parallel, focusing development efforts around key areas of the site that our authors need first. Our stories would exist in a Jira backlog, documentation would be hosted in Confluence , and GitHub would host our codebase. If developers identify technical improvements during the sprint, they can be added as GitHub issues and transferred to Jira if we decide to represent them as stories for the Backlog. For Sprint Retrospectives, @groupmap proved to be a great way to include our remote members of the dev team.

This worked well for our team and allowed us to be flexible in what we wanted to build and how we wanted to build it. As we further defined our Backlog and estimated each story, we could accurately measure the team's capacity (velocity) and confidently estimate a launch date.

10 upvotes·9.7K views

Decision at Katana MRP about Papertrail, appear.in, Bitbucket, Confluence, Intercom, Jira, Slack, RemoteTeam, Agile, CustomerSupportChat, Notes, SourceCode, Logging, Release, InProductCommunication, ContinuousDelivery, Alerts, Documentation, Requirements

Avatar of pk-katana
Engineering Lead at Katana MRP ·
PapertrailPapertrailappear.inappear.inBitbucketBitbucketConfluenceConfluenceIntercomIntercomJiraJiraSlackSlack
#RemoteTeam
#Agile
#CustomerSupportChat
#Notes
#SourceCode
#Logging
#Release
#InProductCommunication
#ContinuousDelivery
#Alerts
#Documentation
#Requirements

As a new company we could early adopt and bet on #RemoteTeam setup without cultural baggage derailing us. Our building blocks for developing remote working culture are:

  • Hiring people who are self sufficient, self-disciplined and excel at video and written communication to work remotely
  • Set up periodic ceremonies ( #DailyStandup, #Grooming, Release calls and chats etc) to keep the company rhythm / heartbeat going across remote cells
  • Regularly train your leaders to take into account remote working aspects of organizing f2f calls, events, meetups, parties etc. when communicating and organizing workflows
  • And last, but not least - select the right tools to support effective communication and collaboration:
  1. All feeds and conversations come together in Slack
  2. #Agile workflows in Jira
  3. InProductCommunication and #CustomerSupportChat in Intercom
  4. #Notes, #Documentation and #Requirements in Confluence
  5. #SourceCode and ContinuousDelivery in Bitbucket
  6. Persistent video streams between locations, demos, meetings run on appear.in
  7. #Logging and Alerts in Papertrail
9 upvotes·1 comment·14.1K views

Decision at Katana MRP about Sketch, InVision, Slack, Microsoft Office 365, Jira, GitHub, Bitbucket, Confluence

Avatar of pk-katana
Engineering Lead at Katana MRP ·

How we ended up choosing Confluence as our internal web / wiki / documentation platform at Katana.

It happened because we chose Bitbucket over GitHub . We had Katana's first hackaton to assemble and test product engineering platform. It turned out that at that time you could have Bitbucket's private repositories and a team of five people for free - Done!

This decision led us to using Bitbucket pipelines for CI, Jira for Kanban, and finally, Confluence. We also use Microsoft Office 365 and started with using OneNote, but SharePoint is still a nightmare product to use to collaborate, so OneNote had to go.

Now, when thinking of the key value of Confluence to Katana then it is Product Requirements Management. We use Page Properties macros, integrations (with Slack , InVision, Sketch etc.) to manage Product Roadmap, flash out Epic and User Stories.

We ended up with using Confluence because it is the best fit for our current engineering ecosystem.

7 upvotes·35.5K views

Decision about Bamboo, Confluence, Jira, Redmine

Avatar of chrisfnz

We were using a hosted version of Redmine to track defects and user stories originally. We migrated to Jira.

Jira was an easy decision for a number of reasons:

  • It's much more "Scrum ready" straight out of the box
  • It's so much easier to keep a track of progress (I love the reporting)
  • It natively encourages you to adhere to Scrum/Agile/Kanban practices
  • Atlassian has a fantastic DevOps ecosystem when considering the likes of Confluence and Bamboo etc
  • So many integrations!
  • Its UI is so intuitive which makes it an absolute pleasure to use!

I know there are alot of other tools in this space but not even considering anything else at the moment. Love Jira!

5 upvotes·7K views

Decision at Uploadcare about Markdown, Slack, slite, Confluence

Avatar of Zmoki
Frontend Team Lead at Uploadcare ·

In Uploadcare we like to write internal documentation and instructions for all occasions. We used Confluence before, but strong and very slow UI fall us to frustration. We start to research alternative and met slite. The ability to quickly create notes and search, great onboarding, the familiar interface in Slack style, useful shortcuts, nice code snippets, support of Markdown. Now writing instructions and team notes have become much more pleasant.

4 upvotes·5.9K views

Decision at Fresha Engineering about InVision, Slack, Confluence, Jira

Avatar of liveweird
CTO at Shedul/Fresha ·

"Soft" part of our development process is handling with: JIRA (which supports our processes & workflows), Confluence (as a knowledge base) & Slack (not only as a collaboration tool, but also as an integration platform for various bots - ChatOps). We use Slack to ask for optimal peer code reviews, create new test environments, etc. We keep UI/UX designs in InVision .

3 upvotes·9.1K views

Decision at Royal Legal Solutions about Confluence

Avatar of swedy13

We have tried hundreds of different software and use dozens of software on a daily basis. Trying to keep up can be challenging. Confluence gives us a central location to store and organize all of the information being generated across the company.

3 upvotes·1.9K views

Decision at Automation Consultants about HipChat, Confluence, Jira, Microsoft Teams

Avatar of jackgraves
Head of Product Development at Automation Consultants ·

We use Microsoft Teams as our primary workplace collaboration tool. It enables our team to work remotely and still collaborate on projects - with integration to JIRA and Confluence, the tool enables us to create War Rooms when problems occur and also provides information-sharing capabilities. Replaced HipChat.

2 upvotes·12.2K views

Decision at Sequoia Consulting Group about Microsoft Teams, Confluence, Jira

Avatar of vishwa161
Fullstack Developer at Sequoia ·

We use Jira for following Agile methodology and Confluence for maintaining Product and Code Documentations. Microsoft Teams for internal team communication

2 upvotes·1.6K views

Decision at MOKA Analytics about Confluence

Avatar of twschiller
Head of Engineering at MOKA Analytics ·

We use Confluence for specifications and knowledge sharing. We chose Confluence over other wikis primarily because of its integration with JIRA Confluence

1 upvote·1.1K views