This document summarizes the tools used by Inventive Designers, including Confluence for documentation, Jira for issue tracking across 3 development teams, and BitBucket for source code management. Pull requests in BitBucket are linked to Jira issues, and custom plugins ensure commit messages and branch names reference associated issues. Jenkins is used for continuous integration instead of Bamboo for cost reasons, and Slack is used for communication instead of HipChat.

1. Atlassian Tools
@ Inventive Designers
ABUG-15
Copyright © 2017 Scriptura Engage

2. Inventive Designers
Copyright © 2017 Scriptura Engage
We provide our own software platform
and related consultative services.

3. Inventive Designers
Copyright © 2017 Scriptura Engage
We help companies improve customer experience and engagement
by providing software for multichannel communications.
• 3 development teams (4-6 people each)
• +/- 15 professional services consultants

4. Copyright © 2017 Scriptura Engage
Index
1
Confluence
4
Other
2
Jira
3
BitBucket

5. Confluence
(Server)
Copyright © 2017 Scriptura Engage
• Human Resources
• Legal documents
• Knowledge base

6. Confluence
(Server)
Copyright © 2017 Scriptura Engage
• Engineering
• Epics: Scoping, Research and technical
details
• Guidelines
• Coding guidelines
• Processes / responsibilities
• How to ...
• ... set up a workspace
• ... use git
• Retrospect reports

7. Confluence
(Server)
Copyright © 2017 Scriptura Engage
• Operations (24/7 support for our own cloud
services)
• Hands-on documentation
• How to connect to server X? at 3 AM ;-)
• Post mortem reports

8. Confluence
(Server)
Copyright © 2017 Scriptura Engage
• Dropbox for sharing other documents (PDF,
Office Documents, ...)
• Also using Dropbox Paper, so not always clear
where to look for a page

9. Guidelines

10. New release page

11. Jira
(Server)
Copyright © 2017 Scriptura Engage
• Engineering (3 teams)
• All new functionality and bugfixes are
tracked in Jira
• Estimate in Story Points, track in hours
• Jira Agile
• Backlog
• Sprints
• SCRUM Boards
• Burndown chart

12. Issue

13. Jira
(Server)
Copyright © 2017 Scriptura Engage
• At the beginning of a sprint, issues are
unassigned
• People choose their next issue
• Find someone to do the code review

14. Agile Boards

15. Jira
(Server)
Copyright © 2017 Scriptura Engage
• 1 shared workflow for all 3 teams
• Limit number of notifications to keep mails
relevant (only send mail when recipient needs
to take an action)
• No subtasks
• Cannot be scheduled on different sprints
• Use “blocks”/”depends on” relation instead
• Avoid writing extensions
• Not our core business
• No time to maintain when it breaks
• Danger of not evolving or
no longer being used

16. Jira
(Server)
Copyright © 2017 Scriptura Engage
Looking at
• Tempo Timesheets
• Track different activities (research, ux, code
review, ...)
• Track non-jira work
• Portfolio
• Track progress
• Plan roadmap
• Predict outcome of different scenarios
• EazyBI
• Report evolution
• E.g. progress of target release date (“we
started on track, then were a little behind,
but now we are ahead of schedule”)

17. BitBucket
(Server & Cloud)
Copyright © 2017 Scriptura Engage
• All code is in BitBucket
• Commits, branches and pull requests are
automatically linked to Jira
• Custom plugin: commit hook that verifies
• Name of issue-branches
• Must start with “issue” and contain reference
to Jira issue. E.g. Issue-SCR-123 or issue/SCR-
123-recursive-delete
• Commit messages
• must contain reference to Jira issue
• Blocks force pushes on shared branches (only
allow force pushes on issue-branches)

18. Pull Request
Change patch (aka “amend commit”/”rebase”) as much as you
want, the pull request will update automatically.
Merge issue-branch to target-branch when ready.

19. Sorry, not using
Bamboo
Copyright © 2017 Scriptura Engage
• Jenkins
• When making the decision back in the day,
the price difference was the main factor (we
have a lot of build nodes)

20. Pull Request builds
Compile and test code before it is merged.

21. Pull Request builds
Compile and test code before it is merged.

22. Sorry, not using
HipChat
Copyright © 2017 Scriptura Engage
• Slack
• Team chats
• Integrations with Jenkins, OpsGenie, ...
• “war” rooms
• Evaluated HipChat and Slack in 2014.
Back then, Slack was a better fit.

23. More info? Contact us:
EU phone: +32 3 425 40 00
US phone: 011 32 3 425 40 00
email: info@scripturaengage.com
Copyright © 2017 Scriptura Engage