Enabling Design Reviews with JIRA and Confluence - Atlassian Summit 2012

Post on 16-Apr-2017

6,004 views 0 download

transcript

Design Reviews with Atlassian Tools

Presenters

Moving Interactive, Inc.

Howard Tiersky & Shaun Collins

Agenda• Who are we and how do

we use Atlassian Tools?• Design Reviews

• Other Topics• Dashboards

• Meeting Minutes

• Integrating workflows with our proprietary deployment tools

• Controlling access to information

• Bonfire for UAT

Who is Moving Interactive?

• Interactive Agency

• Digital products

• Strategy through implementation About 80 people

• 4 years old

• New York, Orlando, and Lima

• Agile

Atlassian Tools at Moving Interactive

Atlassian & Client Collaboration

Clients

+

User Stories

Client tasks

Status Reports

Design Reviews

Developer tasks

UAT/Defects

Time Reports/Billing

Working with Clients to Implement Atlassian Tools for Their Internal Use

• Clear outcomes

• Piloting in our environment

• Installation

• Workflows

• Training

• Ongoing support

“Since [Moving Interactive has] integrated JIRA/Bonfire into our workflow system, it has really

helped streamline communication and overall processes. It has allowed us to create a matrix where stakeholders can see

projects through at every point in the pipeline” Amy Pollack

Website ManagerReader’s Digest

“Moving Interactive is helping Constellation to become more Agile and deliver more effective business results through the way in which we

have implemented iterative methodologies and supported them

by customizing the toolset from Atlassian. It started with their process

but now has become ours.”Michelle McKenna

Chief Information Officer

Constellation Energy

What will this presentation offer you?• Enabling effective collaboration with “customers” whether

internal or external

• Specific tips about how we’ve solved very common scenarios• Design reviews

• Workflows

• Managing UAT

• Meeting Minutes• Controlling access to

information

Design Reviews

Story• As a designer, I can post my

design concepts in one place and view stakeholder comments consolidated.

• As a stakeholder/reviewer I can see the latest and prior designs as well as other comments and can post my own

Story – Acceptance Tests

• Acceptance Tests:

• Quick and easy

• Connect comment to a specific spot in a design

• See history of design revisions and associated comments

• Accessible to clients and internally

• Before: • Designs presented in meetings, via

Got Meeting or via e-mail PDFs

• PDFs sometimes annotated by different people in separate copies

• Lots of email traffic

• Notes taken in various ways, often emailed

• Problems:• Not transparent, notes seen by takers

but not always available to everyone

• Email threads get complex, final decisions get muddied

• Not always clear traceability

• Hard to follow requests for changes and to “tick and tie” all changes made.

• Whose comments are authoritative?

• Old school

• Post PDFs in Confluence and annotate there

• Post image using Balsamiq or Gliffy widget and do annotations in those tools

• Use Bonfire to annotate images the same way we do for UAT of actual web sites

• Use one of the “annotation”/sticky note plugins for confluence pages such as Kwik

Design Collaboration Options

• Cannot add notes to PDFs displayed on confluence page, have to download

• Even if notes are added in Preview/Acrobat, Confluence PDF widget does not display notes

• High likelihood of version conflicts if every one is downloading, reviewing, annotating, and re-uploading.

• Too many steps

PDF Annotation in Confluence

Commenting in Confluence?

• Only 1 comment stream per page

• Comments do not have a way to tie back to a specific spot on a design

• Sticky notes cannot sit on top of an embedded image, so cannot annotate specific spots on an image (other than that, great!)

Sticky Note with Kwik

• These tools work, but they require a bit of getting used to by the client and they are a few too many steps to just add a single annotation. Takes kind of long to load

• Not really meant for annotation

Balsamiq or Gliffy

Close runner up: Screen Snipe

• Multiple users comment on one image

• Interface not hard to learn but not as easy as bonfire

• Requires that image be inserted in a special way

• No record of who or date comment made

• User needs to add initials to know who it is

• Slow to launch Java applet

• Java applets can have security issues on some of our client’s computers that are “locked down”

• Doesn’t create JIRA issues

Close runner up: Screen Snipe

• Very easy to learn

• Launches fast

• Client already knows how to use

• Automatically creates issues in JIRA

• Not perfect though:

• Each persons comments on a separate image

• Viewing images requires opening JIRA issue

• Alow to submit issue under SSL (super fast under http however so may not be an issue for you)

• Initially required filling out too many fields, but solved this problem

Bonfire

Theme from Refined Wiki

https://jira.movinginteractive.com/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project%3D%22MI+Design+Review+test+project%22+and+Design%7E%22rd-design-20120208-tag%22+and+Design%7E%22MI+Design+Review+test+project%22&tempMax=1000

Ignore all this

URL

Dashboards

StoryAs a

developer/manager/client/partner I want to be able to see a high level view of only the key information that pertains to my role so that I can quickly understand the information about a project relevant to me at any time.

Mgr

Dev

Client

3rd Party

Shared Filters leveraging labels

Meeting Notes

Issue & FieldSecurity

StoryAs a developer/manager I want

to be able to record key information onto an issue that should not be accessible to all user types

• JIRA Field Security Plugin• Schemas

• Internal • Client• 3rd Party

• By Fields• Tempo• Estimates• Internal Notes

• By Project

Workflows

StoryAs a developer I want to be able to quickly complete an issue step and have all the proper fields updated and have relevant people automatically notified so that we have high data integrity and people are informed consistently

Acceptance tests:• Depending on a user’s role they should only be able to move

issues to statuses that they have permission to.• External actions such as pushing code via our proprietary

migration tools should update Jira fields and trigger workflows.

• Automated Communication & Notifications• Client Interaction

• 3rd Party Interaction

• Status “Security”• Mapped statuses to roles

• Custom Transition Kickoff • Conditions

• Post Functions

Workflow Transitions Transition Post Functions

• Proprietary tool integration• Automated GIT Commands

• Automated JIRA Issue Updates• By Issue• By Version

• JIRA Comments from Command Line

• Custom Field update• Environment Status• Architect & Developer Notes

Bonfire Testing

StoryAs a user acceptance tester I would like to be able to conduct site review and intuitively and quickly submit identified defects or improvements.

Acceptance tests:• Items go to JIRA directly • Items contain all relevant information• Items in JIRA should be groupable per “round” of acceptance

test• Multiple testers should be able to test at the same time

Sessions

• Singular View of Issues

• Grouping of Raised Issues

• Shared Sessions • By Story/Feature

• By Team

• By User Group

Thank you!