Enabling Design Reviews with JIRA and Confluence - Atlassian Summit 2012


Published on

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Combine with next slides, then add a presentation value slide with takeaways roadmap
  • Add client Anecdote
  • Split into multiple slides, remove tests or make it another slide
  • Add steps?
  • Show Bonfire Session and Template, describe Sessions
  • Quick Views of Dashboards. Split between internal developer and Client PM.
  • Show Bonfire Session and Template, describe Sessions
  • Field Level SecurityHide Time & EstimateConfluence Page Security
  • Add Bonfire Sessions HereAdd Bonfire Test Session DescriptionsExplain Shared Sessions
  • Show Bonfire Session and Template, describe SessionsValidity of data, auto assigning, kick off automated communications…Lightspeed…
  • Add Bonfire Sessions HereAdd Bonfire Test Session DescriptionsExplain Shared Sessions
  • Add Bonfire Sessions HereAdd Bonfire Test Session DescriptionsExplain Shared Sessions
  • Show Bonfire Session and Template, describe Sessions
  • Add Bonfire Sessions HereAdd Bonfire Test Session DescriptionsExplain Shared Sessions
  • Add Bonfire Sessions HereAdd Bonfire Test Session DescriptionsExplain Shared Sessions
  • Show Bonfire Session and Template, describe Sessions
  • Add Bonfire Sessions HereAdd Bonfire Test Session DescriptionsExplain Shared Sessions
  • Enabling Design Reviews with JIRA and Confluence - Atlassian Summit 2012

    1. 1. Design Reviews withAtlassian ToolsMoving Interactive, Inc.PresentersHoward Tiersky & Shaun Collins
    2. 2. Agenda• Who are we and how do • Meeting Minutes we use Atlassian Tools? • Integrating workflows with our proprietary deployment tools• Design Reviews • Controlling access to information • Bonfire for UAT• Other Topics • Dashboards
    3. 3. Who isMoving Interactive?
    4. 4. • Interactive Agency• Digital products• Strategy through implementation About 80 people• 4 years old• New York, Orlando, and Lima• Agile
    5. 5. Atlassian Tools atMoving Interactive
    6. 6. Atlassian & Client Collaboration User Stories Developer tasks Client tasks Status Reports + Design Reviews UAT/Defects Time Reports/Billing Clients
    7. 7. Working with Clients to Implement Atlassian Toolsfor Their Internal Use• Clear outcomes• Piloting in our environment• Installation• Workflows• Training• Ongoing support
    8. 8. “Since [Moving Interactive has] integrated JIRA/Bonfire into our workflow system, it has really helpedstreamline communication and overallprocesses. It has allowed us to create a matrix where stakeholders can see projects through at every point in the pipeline” Amy Pollack Website Manager Reader’s Digest
    9. 9. “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 andsupported them by customizing the toolsetfrom Atlassian. It started with their process but now has become ours.” Michelle McKenna Chief Information Officer Constellation Energy
    10. 10. What will this presentationoffer you?• Enabling effective collaboration with “customers” whether internal or external• Specific tips about how we’ve solved very common scenarios • Design reviews • Meeting Minutes • Workflows • Controlling access to information • Managing UAT
    11. 11. Design Reviews
    12. 12. 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
    13. 13. 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
    14. 14. • Before: • Problems: • Designs presented in meetings, • Not transparent, notes seen by via Got Meeting or via e-mail takers but not always available to PDFs everyone • PDFs sometimes annotated by • Email threads get complex, final different people in separate copies decisions get muddied • Lots of email traffic • Not always clear traceability • Notes taken in various ways, often • Hard to follow requests for emailed changes and to “tick and tie” all changes made. • Whose comments are authoritative? • Old school
    15. 15. Design Collaboration Options • 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
    16. 16. PDF Annotation in Confluence• 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
    17. 17. 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
    18. 18. Sticky Note with Kwik• Sticky notes cannot sit on top of an embedded image, so cannot annotate specific spots on an image (other than that, great!)
    19. 19. Balsamiq or Gliffy• 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
    20. 20. Close runner up: Screen Snipe
    21. 21. Close runner up: Screen Snipe• Multiple users comment on know who it is one image • Slow to launch Java applet• Interface not hard to learn but not as easy as bonfire • Java applets can have security issues on some of our• Requires that image be client’s computers that are inserted in a special way “locked down”• No record of who or date • Doesn’t create JIRA issues comment made• User needs to add initials to
    22. 22. Bonfire• Very easy to learn • Alow to submit issue under SSL (super fast under http however so may not be an issue for you)• Launches fast • Initially required filling out too many fields, but solved this problem• 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
    23. 23. Theme from Refined Wiki
    24. 24. 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
    25. 25. URLIgnore all this 
    26. 26. Dashboards
    27. 27. Story As adeveloper/manager/client/partner I wantto be able to see a high level view ofonly the key information that pertains tomy role so that I can quickly understandthe information about a project relevantto me at any time.
    28. 28. Mgr
    29. 29. Dev
    30. 30. Client
    31. 31. 3rd Party
    32. 32. Shared Filtersleveraging labels
    33. 33. Meeting Notes
    34. 34. Issue & Field Security
    35. 35. Story As a developer/manager I wantto be able to record key informationonto an issue that should not beaccessible to all user types
    36. 36. • JIRA Field Security Plugin • Schemas • Internal • Client • 3rd Party • By Fields • Tempo • Estimates • Internal Notes • By Project
    37. 37. Workflows
    38. 38. StoryAs a developer I want to be able to quickly complete an issuestep and have all the proper fields updated and have relevantpeople automatically notified so that we have high data integrityand people are informed consistentlyAcceptance 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.
    39. 39. • Automated Communication • Custom Transition Kickoff & Notifications • Conditions • Client Interaction • Post Functions • 3rd Party Interaction• Status “Security” • Mapped statuses to roles
    40. 40. Workflow Transitions Transition Post Functions
    41. 41. • 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
    42. 42.
    43. 43. Bonfire Testing
    44. 44. StoryAs a user acceptance tester I would like to be able to conductsite review and intuitively and quickly submit identified defectsor 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
    45. 45. Sessions• Singular View of Issues• Grouping of Raised Issues• Shared Sessions • By Story/Feature • By Team • By User Group
    46. 46. Thank you!