Southeast Michigan AUG - April 25 2018. Hosted at ITHAKA in downtown Ann Arbor.

1. Southeast MI
Atlassian User Group
DANIEL EADS
SUPPORT ENGINEER • ITHAKA
NEIL TAYLOR
LEAD TECHNICAL CONSULTANT • PERFICIENT

2. Where Atlassian users meet
and share best practices

3. Thanks for hosting:

4. Introductions
Name
Company
Role
Experience using Atlassian tool(s)

6. Nancy Brucken
Syneos Health™

7. } Nancy Brucken has been a SAS programmer in
the pharmaceutical industry for over 25
years, with both a pharma company and a
CRO. She is currently part of the Data
Standards and Innovations group at Syneos
Health, responsible for Jira, among other
applications. She is a proud graduate of
Marietta College, and a devout Ohio State fan.
Go Buckeyes!

8. } Introduction
} Basic Agile Development Concepts
} Customized Reporting

10. } Previously tracked projects in shared Excel
workbook
◦ Original VBA macro developers long gone
◦ Workbook easily corrupted
◦ Sharing never worked right in Citrix environment
◦ Adding comments was complicated
} Tracked units (programs/output), but not
time, for planning purposes

11. } Project management application built for use
by programming teams
} CDISC implementation provided hints of use
in tracking programming/validation activities

13. } Sprints
◦ 1-2 week intervals
◦ Programming team commits to completing a certain
amount of work during each sprint
◦ At the end of the sprint, team decides what to do
with anything still outstanding
} Issues = tasks
◦ ADSL dataset program
◦ Program to produce all demographic tables
Sprints consist of issues

14. } User Story
◦ Description of what issue is supposed to produce
} Story Points
◦ Amount of time required to complete the task

15. Set for each
issue type
Typical
program

16. Work performed on issue at each
step
Typical
program

17. Automatic email notification
when issue moved between
steps
Typical
program

18. The project the task
is intended for
What kind of task is
it. Options are:
- Specification
- Program
- Task
The name of the
program or task
The description of the
program or task, e.g.,
the TFL names.

19. A story point is an
estimate of the
amount of time a
program / task is
going to take to
complete

20. Represents a deliverable
Issues can be assigned to
multiple releases
Consists of issues

21. A sprint is a group of
tasks (specifications
and/or programs) to
be completed.
Each sprint should
cover an equal
amount of time.
Normally 1-2
weeks. A release
should be 3 or
more sprints.

22. Activities for each task

23. • Repository for all communication about the issue
• Assign responsibility
• Log comments
• Record changes

24. } Handled via issue screen
} All status changes and comment entries:
◦ Trigger emails to new assignee and anyone else
watching the issue
◦ Automatically logged and stored in underlying
database ChangeGroup, ChangeItem and JiraAction
tables

26. } Burndown Report
◦ Shows amount of work remaining for each sprint
} Velocity Chart
◦ Shows rate of progress

27. Source: Atlassian Jira Software documentation

28. Source: Atlassian Jira Software documentation

29. } Access underlying PostgreSQL database via
SAS/ACCESS to ODBC engine:
LIBNAME jira ODBC DATASRC = '<ODBC
identifier for PostgreSQL database>'
SCHEMA = public
PRESERVE_TAB_NAMES=yes;

30. } Access underlying PostgreSQL database via
SAS/ACCESS to ODBC engine:
LIBNAME jira ODBC DATASRC = '<ODBC
identifier for PostgreSQL database>'
SCHEMA = public
PRESERVE_TAB_NAMES=yes;
Without this option, SAS will not
read tables that do not have valid
SAS names

31. Shows how many times an issue has
cycled between Production and Validation,
and between Programming and Stat QC

32. 1. Identify records for the project
2. Identify records indicating a change in
status from “Validation” to “In Progress”, or
from “Stat QC” to “In Progress”
3. Count the number of records by
combination of old and new status
4. Accumulate a list of the programmers and
statisticians involved

33. } PROJECT table
} NODEASSOCIATION table
} PROJECTCATEGORY table
ID PNAME PKEY
10601 Big Pharma 001 BP001
11096 Meds R Us 015 MRU015
SOURCE_NODE_ID NA_SINK_NODE_ID
10601 10120
ID CNAME
10120 Biostats

34. PROJECT ID SUMMARY
10601 26745 ADAE
ID ISSUEID
31833 26745
GROUPID FIELD OLDSTRING NEWSTRING
31833 status In Progress Validate
31833 assignee Pam Prog Vic Valid
31833 status Validate In Progress
31833 assignee Vic Valid Pam Prog
PROJECT
JIRAISSUE CHANGEGROUP
CHANGEITEM

35. } Count the number of times an issue changes
status by the values of OLDSTRING and
NEWSTRING (records where FIELD=‘status’)
} Accumulate a list of everyone assigned to the
In Progress, Validate and Stat QC records
Code is in the paper

37. } Jira is a useful tool for tracking programming and
validation status of programs
} Easy to set up for projects once workflow defined
} Easy for programmers and statisticians to use in
daily work
} Addition of SAS programs for customized reports
makes Jira a powerful application for project
management and validation documentation

38. Nancy Brucken
Syneos Health
nancy.brucken@syneoshealth.com

40. Version Updates
The latest and greatest
from March & April 2018

41. Confluence
6.8
Mobile apps
Look & Feel
Stability

42. Confluence
6.8
Mobile apps
Look & Feel
Stability

43. Confluence
6.8
Mobile apps
Look & Feel
Stability

44. Confluence
6.8
Mobile apps
Look & Feel
Stability

45. Confluence
6.6
Mobile apps
Look & Feel
Stability

46. BITBUCKET SERVER 5.10
ADG 3
Fresh Look&Feel!
Watch repositories
Get a digest of commit activity
Better email settings
Choose what comes immediately vs
batched in a digest

47. 7.1
3.1
5.10
4.6
5.11

49. Amsterdam & Paris &
Berlin & London &
Austin & San Francisco
& Chicago &
Washington DC

50. Tools +
Practice
Talks
Keynote
Scaling
Atlassian apps
for enterprise
Team Playbook

51. Tools +
Practice
Talks
Keynote
Scaling
Atlassian apps
for enterprise
Team Playbook

52. Tools +
Practice
Talks
Keynote
Scaling
Atlassian apps
for enterprise
Team Playbook

53. In addition to Atlassian
speakers, local customers
from each city also made
short presentations.

54. • ABN Amro
• eBay
• Air France
• T-Systems
• Flixbus
• Open Banking
• Telegraph Media
Group
• Indeed
• Customer panel
(Lyft, Adobe,
Linkedin, Fox
Networks Group
• SAP Fieldglass
• Blackstone
Federal
Customer speakers

55. Top 10 questions asked
(Answered provided by members of the Atlassian team!)

56. 1. Will Cloud + Server
features continue to diverge?

57. 2. Will Trello be available to
Server?

58. 3. Will Jira Software and
Trello merge into one
product?

59. 4. Will the new Jira Software
Cloud UI make its way to Jira
Software Server?

60. 5. How does Trello/Stride
integrate with Jira and
Confluence Datacenter or
Server behind the firewall?

61. 6. When and how can we
migrate from Hipchat to
Stride?

62. 7. Is Stride more expensive
than Hipchat?

63. 8. With hundreds of users in
Hipchat, what will happen to
all rooms and integrations
after migrating to Stride?

64. 9. With multiple teams, how do you find
the balance between standardizing on
common best practices, and also
allowing individual teams the flexibility
to adjust process to fit their
circumstance?

65. 10. When are you going to incorporate
Team Health into Confluence / Jira?

66. Check out more photos on Twitter #AtlassianTeamTour

67. May Support Bar
Tuesday May 1
All evening!
Sweetwaters Coffee
Kerrytown Market
Ann Arbor

68. Thank you!