3 min read

Trello 101: An Introduction

By Luis Machado on Jul 23, 2021 12:21:13 PM

Blogpost-DisplayImage-July_Trello 101 - An introduction

Welcome to Trello 101! In this post, we'll be talking about the basic functionality Trello has to offer that can get you up and running quickly and start managing work for you and your team. We will explore the basic features of Trello and define some of the terminology used. To help illustrate some of these points I've created a template board you can copy over to get started and use to follow along with.

What is Trello?

Trello is an online application used for managing work. It allows for quick and easy team collaboration and empowers you with various methods of customization to tailor your workflow to meet any requirements. Think of it as a glorified digital white board with sticky notes you can use to record and track progress of different tasks! Either with a team or by yourself, Trello offers a way to turn your task list into a visual representation that you can interact with. The level of use ranges from simple beginners to complex power users, with automation and integrations built in. So without further ado, let's take a look at what makes up a board.

Boards

The first thing we need to do is establish what a board is. The board is essentially the personalized site that all of your information lives on: it's where all the organization happens, where you'll setup your workflow, create task items, invite team members for collaboration etc. Boards can be project or team specific, you can create a board for anything, you could even run a D&D campaign off of it. The sky's the limit.

Within the board on the right-hand of the screen lives your board menu. This is where you can manage your team members on the board in terms of their permissions, filter you view through the card search, utilize power-ups or setup any automations.

Trello 101 - An introduction-boards

Lists

Lists are essentially going to represent your workflow. In the example template, the vertical columns are your lists and represent the various stages that your work progresses through. This is the most typical use, but lists can also be used for establishing context on the board. The 'General Information' list houses the instructions for how the board can be used.

Trello 101 - An introduction-lists

Cards

Within the lists we have cards. Cards are the items of work that are to be performed or tracked through the workflow. Whenever you have a new task to track, you can create a card for it with a header and a description, and drag and drop it through the various lists as work progresses. In the template board I've created a few example cards to show the various functionality.

Trello 101 - An introduction-cards

Labels

Labels are a way to group tasks together. In the example of a software development project, you could have labels to represent the different elements like UI/UX, Localization, Codebase etc. In a team management setting you can have different labels for the different groups, you could also use labels to identify priority. They're customizable enough to serve whatever purpose you have for them. In the example board we are using them to identify priority of tasks. You can apply a label to a card by selecting the card and clicking on the 'labels' option in the right side menu.

Trello 101 - An introduction-labels

Adding Team members

Once your board is complete and you're ready to start working, you can invite team members to join your board by clicking on the 'invite' button in the top-middle of the board and adding their email address, or by creating an invite link to allow anyone with the link to join.

Trello 101 - An introduction-members

And that's it! You're ready to rock and roll. I encourage you to use the basic template to get started with to get a feel for how the site works. Once you're comfortable enough with it you can start to branch out into using power ups and automations. 

If you have any question on Trello, or any other Atlassian product, reach out and one of our experts will gladly help!

Topics: blog best-practices tips trello atlassian-products
5 min read

Which Atlasssian Products are Right for my Business?

By Michael Lyons on Jul 13, 2021 9:55:57 AM

Blogpost-DisplayImage-July_Atlassian- Which Application is Right for my Business

Are you considering using the Atlassian toolset, but aren't sure which applications are best for your team or organization? Well I'm here to highlight some of the great applications that Atlassian provides so you can make the right choice for your business. Atlassian's product suite is made up of applications that can unlock your entire organization's potential, from Software Development teams, IT Operations teams and Project Management teams to HR, Legal and Product Owners. You can even use the tools for everyday life! We at Praecipio Consulting love these tools so much that we use them in our day-to-day work.

I will be focusing on a subset of applications that can be used as a starting point for your organization. The applications are great foundational building blocks to start with when using Atlassian for managing work, providing service experiences, or housing documentation. These applications can be used on their own, or they can be used together to maximize team collaboration and efficiency, depending on what suits your team or organization best. 

Jira Software

Teams and organizations can use Jira Software as a tool for managing and tracking work in software development projects. This tool is extremely flexible and can be used by teams that leverage both Agile and Waterfall methodologies. It is highly customizable and can track all sorts of work in the software development lifecycle, including initiatives, epics, stories, and tasks, as well as other items specific to the team. Teams can create customized workflows to track statuses for work items to ensure work is being completed properly and the right individuals are involved to support the work. 

Groups that leverage both Scrum and Kanban can equally benefit from Jira Software. Scrum teams can set work for sprints and track the sprint progress directly in Jira. Visual tools such as boards, dashboards, reports and plans can be used to monitor and execute work. For Kanban teams, Jira's board visual is great for seeing the tasks the team is working on and can help determine where the team needs to focus. WIP (work-in-progress) limits can be set depending on what the team can achieve. 

Software, Gaming, Finance, and so many other types of companies find this tool useful to develop new technology. For example, the development of an App across multiple platforms is an excellent case for leveraging Jira Software. Product Owners can help drive improvements of their Apps with enhanced transparency, reporting, and collaboration through Jira Software. 

Jira Service Management

Teams that provide any level of customer service such as enhancement requests, PTO submissions, or change management often look to Jira Service Management as their main tool. Service desks are useful for taking on requests from both internal and external customers. Requests can be assigned and tracked in the application to ensure customers are getting all the help they need. Companies will also use this application to track changes through the business, such as bug fixes or upgrades. As with Jira Software, Jira Service Management can be customized to fit what the organization needs to ensure great service is being provided.

Organizations use this tool for IT Help Desks. If an employee needs a new laptop or to have a password changed, a request can be submitted through a customized service desk. The requests are sent to teams designated by the organization and can be resolved by those teams. Jira Service Management can be used by other groups within the organization as well, such as Human Resources. As described in one of our previous blogs, HR Teams can leverage service desks to onboard new employees. 

Jira Service Management is used for many different types of requests here at Praecipio Consulting as well. For example, our Marketing Team manages a service desk for Webinars. If someone has a topic to present, the service desk can be used to submit the idea. Once the idea is received, our Marketing team will work with the individual to plan and schedule the Webinar. 

Jira Work Management

Jira Work Management functions similarly to Jira Software, but is geared towards teams that are managing non-software development projects. Project Managers across multiple industries can use this tool to assign and track project work. Similarly to Jira Software, Work Management is customizable and provides great visualizations to monitor work and ensure projects are being completed on time. 

This tool doesn't just have to be used for company-related work: it can be used outside of work as well. For example, searching for a new house! The house buying process is extensive, and Jira Work Management can help outline tasks, assign work, and set dates and dependencies so you can purchase your next home in an organized manner.

Confluence

Confluence is a robust content management tool that teams can use to house important project materials, knowledge resources, and document templates. Within Confluence, spaces can be created for organizations and teams to organize documentation. Then pages can be created within the space where teams collaborate and share notes and documents on work being completed. This application can work for any sort of organization in any field, not just for technology groups. 

This application can be used to document daily meeting notes, standard best practices for an organization, and much more. Confluence can incorporate helpful macros to enhance the information being shared. For example, macros include drawing features for diagrams and templates for consistency across documentation. This application enables all of your teams and stakeholders to communicate effectively about projects.

How Can Applications Be Used Together?

I've discussed a small group of the tools that Atlassian offers. These applications can be used on their own, and you may feel the need to only use one. However, if multiple applications fit your needs, you can use them together to achieve operational excellence.  A common case is leveraging confluence and combining it with other Atlassian applications. Confluence, being a great documentation tool, combines extremely well with the applications discussed. Below you will see these combinations and effective use cases for each.

Confluence and Jira Software:  Confluence can be used to document daily notes for scrum meetings and create templates for how retrospective meetings should be organized. It can also be used to store any internal team notes on work being completed.

Confluence and Jira Service Management: Confluence can hold documentation on how to resolve a specific issue pertaining to the business.

Confluence and Jira Work Management: Confluence can be used to document discovery sessions about the project or even store your robust project plans. Drawings can be added to confluence as well for reference. 

The immense synergy between Confluence and all of these applications can help maximize the benefits of your Atlassian applications!  If you have questions about any Atlassian applications, please reach out to us, we would love to help! Best of luck in your Atlassian journey!

Topics: jira blog confluence jira-service-desk jira-software atlassian-products jira-work-management
2 min read

Get early access to Atlassian Data Lake for Jira Software

By Kye Hittle on Apr 23, 2021 2:00:00 PM

Blogpost-display-image_Jira Data Lake Preview

What's a data lake?

Read up on the basics in our explainer.

At Praecipio Consulting we understand that the data contained within your Atlassian tools is a critical asset for your organization. To help customers more easily access their Jira data, Atlassian has developed Data Lake! As of March 2021, Data Lake is available to preview in Jira Software Cloud Premium and Enterprise.

Warning! Beta software should not be used for production purposes. Breaking changes are likely as Atlassian tweaks this functionality based on user feedback. Not all Jira data is currently available and permission levels are limited but Atlassian is quickly working through its roadmap. In addition only English field names are available, as of now. Therefore, any information presented here is subject to change.

Data Lake allows you to quickly connect the best-in-class business intelligence (BI) tools you've already invested in to query the lake directly.

Compatible BI Tools include:

  • Tableau
  • PowerBI
  • Qlik
  • Tibco Spotfire
  • SQL Workbench
  • Mulesoft
  • Databricks
  • DbVisualizer

Jira-Data-Lake-preview

Data Lake uses the JDBC standard supported by many BI vendors. Supporting an open standard provides tremendous flexibility and power in reporting on your Jira projects.

Once you've identified the components of your BI solution, you'll follow three basic setup steps:

  1. Configure the JDBC driver
  2. Connect your BI tool(s)
  3. Navigate the Jira data model

You'll need your org_id and an API token for your Jira Cloud instance. Except for creating an API token (if you haven't already), there's no config required within your Jira instance. There are instructions for connecting to various BI tools in the Atlassian community Data Lake Early Access group. In addition, you'll find posts and diagrams to assist in answering business questions using Jira's data model.

If you're a Premier or Enterprise customer and would like to access the Early Access Program for Data Lake, complete this form to request access. You can also post questions and feedback for the devs in this group.

Are you interested in unlocking the power of data stored in your Atlassian tools? We're a Platinum Atlassian partner with years of experience helping customers leverage their Atlassian investment for even more value, so get in touch!

Topics: jira atlassian blog enterprise jira-software atlassian-products business-intelligence data-lake
4 min read

Why Upgrade Your Atlassian Stack?

By Suze Treacy on Apr 16, 2021 11:18:00 AM

Blogpost-display-image_Why Jira-Confluence upgrades are importantOne key component of managing your Atlassian products is managing their upgrades. Upgrades can present a daunting and significant time investment for many companies, generally involving apps, custom-developed plugins, and integrations, with a large number of users dependent on their success.

You know what upgrades are and that they're important. So why am I talking to you about them? Imagine the scenario, you're busy, you haven't had a chance to check in on the latest Atlassian security vulnerabilities and the emails you've received about them have been missed. You have also had higher priority work eating up team time, which has prevented the planning and execution of your Atlassian upgrades. One day, your instance comes under attack through one of the vulnerabilities exposed in the CVE. Your data is potentially exposed. An urgent, large, expensive, complex effort ensues in order to secure the instance; after 3 days, 2 full sweeps of the instance and multiple upgrades, the vulnerabilities are mitigated and your instance is safe.

Are you confident in when your applications are due an upgrade? Let's review a few common reasons why an upgrade may be recommended:

End of Life Policy

Once Atlassian has released a major feature version, it, and all iterations related to that major version, are supported for two years. After that, the versions are considered End of Life, and you will no longer receive support from Atlassian for any issues which arise. It is when reaching this point, that many people start considering upgrading their instances.

Security Vulnerabilities

Every Wednesday, Atlassian releases any new security vulnerabilities which have been identified for their server/data center products. These vulnerabilities include a security level, which is based on an Atlassian-calculated CVSS score for each vulnerability.

Severity Rating System followed by Atlassian:

Atlassian_severity_rating_system

Although there may be opportunities to mitigate security vulnerabilities in your current version, it is recommended to patch or upgrade immediately when a Critical vulnerability is identified. Vulnerabilities with a critical score generally result in root-level compromise or servers or infrastructure devices, or are straightforward to exploit.

Current security advisories can be found here:

https://www.atlassian.com/trust/security/advisories

New Functionality/Capabilities

Did you know that there is a new feature release for Jira Software every 6 weeks alone? Atlassian encourage users to submit bugs and feature requests at jira.atlassian.com. This public forum allows users to vote for and comment on submitted issues, and the Atlassian team utilize this and other feedback as a factor in their decision for what to implement next.  Platform releases contain the most significant changes, while Feature releases contain new features, changes to features, changes to supported platforms and removal of features. Feature releases can be designated as Enterprise releases, which, generally designated annually, are preferred for companies who need time to prepare for upgrades, but still want to receive critical bug fixes.

Compatibility with other Server Components

From time to time, Atlassian add and deprecate support for other server component platforms which work alongside your Atlassian application. For example, did you know that in Jira Software 8.6 and Jira Service Desk 4.6, support was added for PostgreSQL 10 and deprecated for Internet Explorer 11, whereas in Jira Software 8.8 and Jira Service Desk 4.8, support was deprecated for Microsoft SQL Server 2012 and PostgreSQL 9.4 & 9.5. To ensure optimal operation of your Atlassian instances, it's just as important to upgrade components of your server architecture, as well as your instances themselves.

Plugin Support

If you are one of the many teams who utilize plugins within their Atlassian applications, plugin compatibility and support is another area to be aware of when considering upgrades. Has support been deprecated for the plugin with the Atlassian version you're running? Is the plugin still supported when you upgrade to your target version? Atlassian have developed the Universal Plugin Manager, available in both Jira and Confluence, to enable you to screen for any compatibility problems prior to starting your upgrade. There are 4 categories for Compatibility which plugins can fall into - Incompatible (the plugin is not compatible with the target version), Compatible, Compatible if updated (the plugin is not currently compatible, but will be once running the compatible version), and Compatible once both are updated (the new version of the plugin isn't compatible with your current instance version - you need to upgrade your instance prior to updating the plugin).

Unable to Skip a Platform Release

When considering which version you'd like to upgrade to, it's important to consider your current version and your target version. When upgrading, it is not possible to skip a platform release - therefore, for example, when considering a Jira Software upgrade, it is not possible to jump from a 6.X release to the 8.X release and skip the 7.X release, you would need to take an intermediate step to upgrade to a 7.X version. Due to the functionality changes being much greater between platform releases which are not adjacently sequenced, there are more edge cases, and thus, greater risk, when navigating an upgrade spanning multi platform releases.

For assistance with upgrading your applications, partner with Praecipio Consulting's Managed Services team! Our team, fully dedicated to the Atlassian stack, offer peace of mind through managing, supporting, and maintaining your Atlassian tools, enabling you to maximize the benefits of your Atlassian applications while allowing your team to focus on their core roles. Working with our Managed Services team offers tribal knowledge and best practice from over 10 years working in the tools, allowing us to enable your Atlassian stack is optimized and operating at peak performance.

For more information on Managed Services, or anything else Atlassian related, contact us, and one of our experts will be glad to talk with you.

Topics: blog managed-services marketplace upgrade version-control-system atlassian-products marketplace-apps
2 min read

Praecipio Managed Services: The power of a part-time, full-stack Atlassian admin

By Suze Treacy on Feb 18, 2021 12:50:00 PM

Blogpost-display-image_The power of a part-time, full-stack Atlassian admi-1Do you find yourself tasked with administering Atlassian tools on top of the normal duties of your job? Have you ever been faced with an Atlassian question that is out of your wheelhouse? Are you interested in improvement opportunities to configure your instance and architecture to Atlassian best practice standards? If you answered yes to any of these questions, then read on!

With a wide range of Atlassian products available, and a marketplace full of apps to accompany those, it's hard to find admins who specialize in everything. Particularly with the Atlassian toolset being highly configurable, administrators should be able to analyze a request and advise the correct path forward, balancing functionality available to them, with corporate governance and best practice processes. Here at Praecipio Consulting, we have the answer to this unicorn, part-time, full-stack Atlassian admin, through our Managed Services offering.

Atlassian Experts, Best Practice

With over 10 years of Atlassian experience, our team has knowledge across the full stack - whether your question is about hosting considerations, tuning, networking, infrastructure, process-related, Marketplace Apps, or anything else, we can advise and implement functional, practical, industry-specific, best practice processes to maximize efficiencies among your teams. As we are squarely focused on the Atlassian toolset, your IT teams can focus on all of their other tasks, driving productivity and innovation among your team.

Preventative Measures

We're proactive, with bi-monthly cadence calls to discuss your long term goals and objectives, and monthly health checks to ensure your instance is secure, clean, and performing efficiently. We monitor Atlassian vulnerabilities, alerting you of any CVEs affecting your instance, alongside recommendations to mitigate. If you are hosting with us through Cumulus, we monitor your systems too, identifying and resolving issues before they become expensive incidents, and minimizing downtime.

Predictable Cost, Scalable Model

Whether you're utilizing Atlassian Cloud, Server, or Data Center, whether you need 9-5 support, or 24x7, we're always here to help. You dictate your monthly hours cap, enabling Atlassian administrative support at a fraction of the cost of hiring an admin. Even with the cap, it's possible to utilize more hours - managed services is scalable as your business and Atlassian needs grow.

Relationships

As Platinum Enterprise solution partners to Atlassian, we're big on relationships with our clients, Atlassian, and App vendors. When faced with issues, we can be the connection between yourselves and the answer you need, to discover the optimal outcome available for your circumstances. We're vested in your instances being healthy and working for your business: allow us to be a trusted partner in helping your business grow.

Praecipio Managed Services can help with your Atlassian needs, we'd love to talk to you more about our offering! 

Topics: atlassian blog implementation managed-services atlassian-products bespoke
3 min read

Individuals and Interactions Over Tools Doesn't Mean No Tools

By Morgan Folsom on Feb 1, 2021 11:00:00 AM

Blogpost-display-image_People & Process over tools doesnt mean no tools-1"Individuals and interactions over processes and tools"

It's an important line from the Agile Manifesto – one that establishes that the focus when trying to work in an Agile way is the people. However, we often see this used as a justification to provide inadequate tools to teams. In a well-run Agile organization, you shouldn't have to think about the tools - they should support the work that the team needs to do without getting in the way. Organizations often make the mistake of implementing tools to make teams work in an Agile way. However, tools are in and of themselves not enough - the people and processes behind them are what makes a business go.

However, this doesn’t mean we should ignore the tools we use, opting for whatever’s cheapest, easiest to setup, what we’ve always used, or something that’s “good enough.” Rather, we should take the exact opposite approach and select our tools purposefully, deliberately identifying the tools which best empower employees and promote processes. Because of this, there are two properties of utmost importance when considering a new tool: the tool should allow our team to run with the process that best meets our team’s needs, and the tool should help our team members work better together.

To fit the first of these criteria, the tool should be customizable in a way that allows your team to use your own process. Much of enterprise software today shoehorns teams into predefined configurations and settings which the tool manufacturer thinks are best. This leads to frustration, difficulty in using the tool, and potentially costly transitions to new software. In our experience, every team is at least a little bit different, and even two teams that want to implement the same fundamental process will find they have a few differences they would like reflected in the process. Because those differences tend to arise from the uniqueness of your team, they are important to capture in the tool in order to give your team the tools that best meet your needs.

Further, a good tool will promote communication and collaboration between teammates, inside or outside of the tool. Information tends to get lost when team members do their work in one system but communicate that work in another. For this reason, an ideal product will allow for conversations to take place within the product, ideally directly on the work item those conversations are referring to. Historical conversations should be preserved to allow for a look back on what decisions were made and why, and the tool should have options for how users are notified of important communications. Further down the collaboration path, handoffs should be made simple if not automatic, and any approvals should be doable within the tool. Finally, high-level or detailed status reports should be visible and accessible by any team member who needs or wants to see them.

These two crucial properties are two of the reasons we like Jira. Atlassian’s strategy for a long time has been to develop applications to meet the 80% of needs that are shared by most teams, such as collaboration features, malleable processes, and easy visibility of work, while allowing the remaining 20% of needed functionality to be determined by individual teams and sourced in the Marketplace. The result is a product which delivers good performance out of the box, but can be optimized to meet the needs of any team.

Consider the role that Jira plays in Agile. A large portion of the functionality is built in: Kanban and scrum boards, backlogs, issue types, workflows, and sprint reports. However, the software is customizable to the point that it works equally well for teams that have a quick, simple process with a few issue types and teams which have a complicated process with several rules, handoffs, and types of work. It doesn’t matter to Jira whether your version of Agile requires multiple manager sign-offs before it’s done or if your team lives on the edge, skips QA altogether, and goes straight to production. The point is that the software fits your process, not the other way around. Regardless of process, there are several mechanisms for the team to stay in touch along the way. Every issue can be commented on and allows for @-mentions to draw attention quickly. Email notifications are sent out at times decided by the team, not at arbitrarily defined times decided by the tool’s developers. Progress is simple to see on a board, and every user has access to generate reports or build dashboards to collect information relevant to them, reducing the need for repetitive status reports.

Most organizations will purchase a tool, kick it around for a few years, then junk it because it “doesn’t work right” or “doesn’t make sense for us.” Don’t let this happen to your organization. Pick your tools with care and optimize them for your team. And if you need help, talk with the experts, and get great advice!

Topics: jira blog best-practices tools atlassian-products agile
4 min read

What's the deal with Atlassian's Jira Cloud migration tool?

By Bradley Ode on Jan 14, 2021 10:45:00 AM

Blogpost-display-image_Whats the deal with Atlassians Jira Cloud migration tool (1)Atlassian's Jira Cloud is more popular than ever as companies continue to see the benefits in cloud-based technologies. For those of you already on server, the latest announcement from Atlassian might prompt you get to a head start on looking at migration options. I had the opportunity to work with Atlassian's Jira Cloud Migration Assistant (JMCA) earlier this year and now is a more pertinent time than ever to share those findings. 

What is the Jira Cloud Migration Assistant?

Jira Cloud Migration Assistant is an add-on introduced by Atlassian earlier in 2020 to help clients migrate their data from Server to Cloud. It is a migration assistant and should be viewed as such. There are many things that JCMA does well, but it does come with it's limitations and should not be viewed as a one-and-done solution for most organizations. With that being said, companies with small Jira Server footprint will get the most use out of the tool.

At a glance

What can it do?

  • Jira Software and Jira Core Project data
    • Details
    • Roles
    • Screens and Schemes
    • Workflows
      • Most native workflow functions
  • Issue data
    • Most custom fields
    • Issue history
    • Rank
    • Worklogs
    • Attachments
    • Comments
  • Boards linked to projects being migrated
  • Active users and groups from User Directories

What are the limitations?

  • Jira Service Management- no Jira Service Management data can be brought over with JCMA at the time of publishing
  • Third party app data
  • User Avatars/Timezones/Passwords
    • Passwords will need to be reset after migrating unless the client is using SSO
  • Global configuration items
    • Since JCMA operates at the project level no system settings will be brought over
  • Certain custom fields
    • Single and Multi-version picker
    • URL
    • Select List (cascading)
    • Select List (multiple choice)
    • Project picker
  • Certain workflow functions
    • Validator: required field, field changed
    • Condition: user in group, in project role, field value, subtask blocking
    • Post Function: clear field value, update custom field, copy value from other field, delegating
  • Links to entities that are not migrated

I don't have Jira Service Management, but what's this you say about app data?

Unfortunately, Marketplace Apps will need to be handled on a case-by-case basis. The JCMA tool provides a mechanism for assessing which apps can be migrated from server to cloud, but does not migrate the data via the tool itself. Instead, the tool will scan your instance and provide links or paths (i.e. instructions) to external documentation if it exists.

These paths can be a bit confusing as you are taken to the individual app vendors' sites. These can be radically different from app to app. In our case, many apps did not have a path forward and, instead, we are prompted to contact the vendor.

What about users?

JCMA will bring over all active users and groups on each migration initiation (which may or may not be what you want). You have the option of giving the users product access before running the migration, but in my opinion, it is best to wait until after the migration in case things go awry. After running the migration, the users will need to be invited to the Cloud site.

Should I use JCMA? Or perhaps another method like site import?

When the instance to be migrated is small, well managed, and with little complexity, the JCMA tool will handle your data with finesse. The JCMA tool is also more useful in merges when you are trying to merge a small, relatively simple Jira Software Server instance with a larger cloud instance. This is due to the fact that the JCMA tool itself is very project-centric. However, an abundance of app data, complex workflows, and many external integrations can be some of the things that might stop an organization from using this tool. If you are in any way unsure, contact us -- we've got your back.

My Experience

Overall, I found the JCMA tool to be a simple and effective way to transfer small amounts of project data to a cloud instance. It does what it says it will do, with only minor hiccups along the way. My experience a few months back is likely going to be different with yours as Atlassian continues to invest heavily in Cloud offerings. As always, do your own reading and don't be afraid to ask for help.

Further Reading

Topics: jira blog migrations cloud atlassian-products
3 min read

Atlassian Certification Program: Tips for Studying for your ACP Exams

By Rebecca Schwartz on Oct 21, 2020 12:45:00 PM

Blogpost-display-image_Atlassian Certification Program- Tips for studying for your ACP exams-1

Atlassian Certification Program (ACP) exams are a great way to enhance your Atlassian skillset and better leverage the tools at your organization. Atlassian offers a few different exams, depending on what aspects of the tools you're focused on and your current skill level. If you pass, you get a nifty badge you can place on your LinkedIn profile or email signature! Here at Praecipio Consulting, all of our consultants have taken at least one of the available ACP exams, and we have some great tips and tidbits to share that will help you prep for the tests and understand what they entail.

A little bit about the exams

  • Atlassian offers 6 different ACP exams
  • Exams are typically between 70-80 questions
  • Exams can be taken remotely due to COVID-19, but are proctored
  • Depending on the exam, the passing score is between 60-70%
  • You have 180 minutes (3 hours) to complete your exam

Take it back to your college days with study guides and flashcards

When studying for any exam, it's important to figure out how you best learn the material. Is it taking notes by hand so you don't have the distractions of a laptop? Or, are you more like me, where you tend to lose loose leaf paper so you prefer to type out what you've learned? Either way, the best tip I used to prepare for my exams was to organize my notes into a comprehensive study guide. Atlassian requires the completion of specific courseware before you can take the exams, and they provide downloadable PDFs for each exam topic. All of this information is great for your study guide. You can use a good ol' fashioned notebook for this, or, if you have access to Confluence, create your study guide there. I took notes on the courseware in Confluence, then used macros and Tasks to organize my notes and remind myself of topics that I needed to focus on. Because the exams cover a lot of material, flashcards are another great way to memorize information. There are several online services that allow you to create flashcards for free, such as Quizlet. Repetition works wonders when studying for any exam, so be sure to review your study materials several times.

Practice in a test environment

If your way of learning is by doing, a great way to prep is by reviewing admin functionality in your Jira or Confluence instance, especially if you have a test or demo environment. Project schemes, permissions (project and global), and workflow functionality can provide helpful knowledge around exam items. Chances are, if you're taking an ACP exam, you already have access to a Jira and/or Confluence environment, but if not, Atlassian offers a free Cloud instance if you're maintaining 10 users or less. Keep in mind that some exams only focus on Server functionality, but it's still great to get a visual for the items you'll be tested on.

Collaborate with others prepping for the exam

At Praecipio Consulting, we are all about teamwork. As I was prepping for my exam, so were several other Praecipians. We collaborated on our notes, shared our study guides, and had study groups. Sharing our thoughts and notes allowed us to each figure out our strengths and weaknesses around the exam material so we could help each other be successful. If you're the only one at your organization taking the exam, or are just deciding to do it individually, no worries - there are folks all around the world looking to get certified! If you venture over to the Atlassian Community, there are often discussions that folks have started to create study groups with members of the community (check out this post around the ACP-100). 

Stay in tune with your physical and mental state 

Prepping for and taking any exam is physically and mentally exhausting. It's important when studying to allow yourself breaks to better absorb the material. As I studied, I'd create incentives and goals around my study material. Once I got through half of my flashcards, for example, I'd watch the next episode of my newest Netflix addiction or read a chapter of my favorite book. That way, I had something to look forward to when studying and allotted plenty of time for brain breaks. When it comes to taking the exam, try to find a quiet space in your home where you can remain undistracted. If you get stuck on a question, mark it and come back to it - you've got 3 hours to get through the questions, so take your time! Remember, your well-being is a key factor in being able to focus and perform your best, so it's important to keep it in check.

Good luck with your next exam, and let us know if your organization needs further support with how to best leverage your Atlassian applications. 

Topics: atlassian blog agents training atlassian-products atlassian-certification-program
3 min read

Challenges in Managing Your Own Atlassian Instances

By Morgan Folsom on Oct 2, 2020 12:30:00 PM

Blogpost-display-image_Challenges in managing your own Atlassian instances

Are you having trouble managing your Atlassian instances? As tools like Jira become mission-critical to organizations, it's increasingly important that their maintenance is formalized, with dedicated resources who manage the tools. Let's walk through a few of the biggest challenges that we see and how Praecipio Consulting's Managed Services offering can help ease the pain.

 

Can you help if we don't have the technical experience to support the tools?

It's not uncommon that teams find themselves struggling to manage the specifics of Atlassian. Just because you've got a killer IT team doesn't mean they'll be experts on a whole new platform on day one! There are a lot of intricacies to the tools that can take admins a while to understand, especially when we're looking at Jira. On top of figuring out the technical aspects of maintaining the tools, you're also expected to help make process recommendations and changes for the teams that use the tool at your company. 

One of the biggest benefits of using a Managed Services provider is that you don't have to develop all of the in-depth expertise on the tools, because we've been there and done that. Our focus on the Atlassian suite means that we know the tools better than anyone so that in addition to answering your requests, we can anticipate issues because we know what to look for. 

What about about if our IT team is too small to have dedicated admins?

Maybe your team are experts at managing the Atlassian suite, but you're missing one major thing: time. Keeping your instances healthy requires ongoing maintenance, dedicating time for things like platform upgrades and marketplace app configuration, as well as triaging requests from your users to make the tools work for them. This is something that affects teams of all sizes and can be especially painful if you're part of a small organization. When you don't have dedicated Atlassian admins, the impact on your instances can be huge. If teams are only able to focus on addressing breakfixes and user requests, things like upgrading your marketplace apps can fall by the wayside. 

Our Managed Services team excels at thoroughly preparing for and executing upgrades, and regularly checking to make sure your instances and apps aren't affected by any critical security issues. 

Or what if we've moved to Cloud and don't know what administration we need to do anymore?

If you're one of the many organizations that have moved from hosted Server or Data Center instances to Atlassian's Cloud, you've probably realized that administration looks a little different now. Because a lot of the technical maintenance tasks aren't necessary anymore (woohoo!), your team gets to focus on making sure the instance is healthy from a process perspective. This kind of administration requires different skills from your admins – and while they hopefully have been providing this before, it's easy for this to fall through the cracks. 

Administration isn't just about creating workflows or fields, but making sure that the configuration in the instance aligns to industry and Jira best practice. Jira in particular is extremely configurable – with the right combination of apps and know-how, you can do basically anything, for better or worse. A lot of common configuration choices can be setting you up for future headaches – things like too heavy a reliance on scripting when out-of-the box configuration can do the same thing, making upgrades a pain and causing negative performance impacts. 

If any of the concerns above strike a chord, let us help

Topics: atlassian managed-services cloud atlassian-products atlassian-solution-partner
4 min read

Turn Your Next Project into a Promotion

By Christian Lane on Oct 1, 2020 1:15:00 PM

Blogpost-display-image_Do These Things to Leverage a Successful Project Into a Promotion

Make this next project the one that gets you noticed.

Kate Cornell was in a tough spot. Her fast company growth exposed a weakness. Her project management tools were a collection of cobbled-together solutions that were never purposely developed for case management or tracking complex projects. As a result, the team was fragmented and communications were inefficient, making work difficult to track. 

There had to be a better way. When the problem was presented to the management team, she was tasked with figuring it out.

Smartly, she knew that she needed some specialized help in not only choosing a platform but configuring it to meet the present and future needs of the company. After vetting multiple vendors, she chose Praecipio Consulting, a Platinum Atlassian Partner known for their strategic approach and ease to do business with, not to mention their expertise around the Atlassian platform.

katie aci blog post

In her role as the Director of IT Project Management for ACI Worldwide, it’s her responsibility to make sure projects like these are executed well. The company depends on it - careers depend on it.

Thankfully, this project was an enormous success. In a double win, the company was able to save significant costs and the Atlassian technology stack is exactly what they needed.  

Now that the project is complete, we asked her to reflect on the process and what she would recommend to others faced with a similar challenge.

Tell us about the vendor and how they performed for you. 

“I knew from the get-go that this is a project we needed help with. We used our previous CRM-based system for 10+ years, and there was an incredible amount of data that needed to be migrated over. But what impressed me most was their ability to ask questions and gather requirements. You can tell they had lots of experience. They led us in directions we didn’t know we needed to explore.”

What did success look like?

“I’m calling the project a huge success - first, because the solution works well. The data moved over, and we finally have everyone on the same tool. It’s nice to have a framework that is purpose-built for what we need. We’re able to move faster and with more efficiency than ever before. What I’m most proud of though is the broad adoption among our team. It’s hard to break out of your routine and use something new. Going through a necessary learning curve is difficult and cumbersome, but our team bought into the long-term vision and saw the value immediately.

What advice would you give project managers that want to fast forward their careers with a project like this?

Don’t operate in a silo. Design an escalation process so that when you get stuck, you can bring in other stakeholders to work toward a solution. Transparency is key. Managers don’t like surprises. They understand challenges will arise and usually, they are willing to help. But make sure you have a plan to execute and not just a problem with no solution. 

Set realistic expectations. I want my managers to commit to running at a rate of speed they feel is appropriate considering they have multiple projects. If we are managing the business correctly, everything is not an emergency. I can wait an extra two weeks if it means the project is done right the first time. 

Clearly define done. Ambiguity is a productivity killer and it can ruin relationships. The best managers we have err on the side of over-communication versus under. Making sure all relevant team members are aware of progress milestones, have an opportunity to provide input, and understand how this project fits within our overall mission is how it should be done. 

Be predictable and reliable. Successfully handling projects that deliver on time and within budget earns you a reputation as someone who delivers results. Our best managers are the ones that use company resources wisely and think one step ahead of the task at hand. This strategic mindset gives managers comfort knowing that they don’t have to worry about micromanaging.

Praecipio Consulting's take on how to leverage a successful project:

In our experience, we have seen how production-based project managers have climbed the ladder of success. One common theme? They make others around them better. Getting the most from your team and developing the talent of tomorrow has far-reaching implications for any company. At Praecipio Consulting, we are in the business of making our clients more competitive while helping them realize cost savings through better processes and better technology. IT project managers that have an upward career trajectory tend to not get caught up in technical jargon and can talk to the C-suite in terms of ROI and how the project fits into the strategic plan.

One thing all experts agree on is that communication between management, engineers, vendors, and even other third parties will mitigate the risk of a project losing momentum or failing. If your communication skills can match your ability to motivate teams and deliver technical projects, you’ll be asked to take on more and more important projects and be rewarded accordingly.

If you're interested in the game-changing solutions that Atlassian products can bring to your business, let's chat!

Topics: enterprise project-management atlassian-products atlassian-solution-partner
4 min read

Why You Should Upgrade Your Atlassian Stack

By Suze Treacy on Sep 4, 2020 12:15:00 PM

Blogpost-display-image_Why upgrade your Atlassian stack-

One key component of managing your Atlassian applications is managing their upgrades. Upgrades can present a daunting and significant time investment for many companies, generally involving applications, add-ons, and integrations, with a large number of users dependent on the success

You know what upgrades are and that they're important. So why am I talking to you about them? Imagine the scenario: you're busy, you haven't had a chance to check in on the latest Atlassian security vulnerabilities, and you've missed the email updates based on your subscription. 

You also had higher priority work eating up team time which has prevented the planning and execution of your Atlassian upgrades. One day, your instance comes under attack through one of the vulnerabilities exposed in the CVE. Your data is potentially exposed. An urgent, large, expensive, complex effort ensues to secure the instance; after three days, two full sweeps of the instance and multiple upgrades, the vulnerabilities are mitigated and your instance is safe.

Are you confident you know when your applications are due for an upgrade? Let's review a few common reasons why an upgrade may be recommended.

End of Life Policy

Once Atlassian releases a major feature version, it, and all iterations related to that major version, are supported for two years. After that, the versions are considered End of Life and you will no longer receive support from Atlassian for any issues which arise. This is when many Atlassian Administrators start considering upgrading their instances.

Security Vulnerabilities

Every Wednesday, Atlassian releases any new security vulnerabilities which have been identified for their server/data center products. These vulnerabilities include a security level, which is based on an Atlassian-calculated CVSS score for each vulnerability.

Severity Rating System followed by Atlassian:

Screen Shot 2020-06-03 at 8.40.10 PM

 

Although there may be opportunities to mitigate security vulnerabilities in your current version, it is recommended to patch or upgrade immediately when a Critical vulnerability is identified. Vulnerabilities with a critical score generally result in root-level compromise, servers or infrastructure devices, or are straightforward to exploit.

Current security advisories can be found here.

New Functionality/Capabilities

Did you know that there is a new feature release for Jira Software every 6 weeks alone? Atlassian encourages users to submit bugs and feature requests at jira.atlassian.com. This public forum allows users to vote for and comment on submitted issues. Then, the Atlassian teams review this and other feedback as a factor in their decision for what to implement next. Platform releases contain the most significant changes, while Feature releases contain new features, changes to features, changes to supported platforms, and removal of features. Generally designated annually, feature releases are preferred for companies who need time to prepare for upgrades, but still want to receive critical bug fixes.

Compatibility with other Server Components

From time to time, Atlassian adds and deprecates support for other server component platforms, which work alongside your Atlassian application. For example, did you know that in Jira Software 8.6 and Jira Service Desk 4.6, support was added for PostgreSQL 10 and deprecated for Internet Explorer 11? In addition, in Jira Software 8.8 and Jira Service Desk 4.8, support was deprecated for Microsoft SQL Server 2012 and PostgreSQL 9.4 & 9.5. To ensure optimal operation of your Atlassian instances, it's just as important to upgrade components of your server architecture as well as your instances themselves.

App (Plugin) Support

If you are one of the many teams who utilize Apps (plugins) within their Atlassian applications, plugin compatibility and support is another area to be aware of when considering upgrades. Has support been deprecated for the plugin with the Atlassian version you're running? Is the plugin still supported when you upgrade to your target version? Atlassian has developed the Universal Plugin Manager, available in both Jira and Confluence, to enable you to screen for any compatibility problems before starting your upgrade. There are 4 categories for Compatibility which plugins can fall into:

  • Incompatible: the plugin is not compatible with the target version
  • Compatible: No adverse impacts to the target version
  • Compatible if updated: the plugin is not currently compatible, but will be once running the compatible version
  • Compatible once both are updated: the new version of the plugin isn't compatible with your current instance version and you need to upgrade your instance prior to updating the plugin

Unable to Skip a Platform Release

When considering which version you'd like to upgrade to, it's important to consider your current version and your target version. When upgrading, it is not possible to skip a platform release. For example, when considering a Jira software upgrade, it is not possible to jump from a 6.X release to the 8.X release and skip the 7.X release. You must take an intermediate step to upgrade to a 7.X version. Due to the functionality changes being much greater between platform releases that are not adjacently sequenced, there are more edge cases, and thus, greater risk, when navigating an upgrade spanning multi-platform releases.

For assistance with upgrading your applications, partner with Praecipio Consulting's Managed Services team! Our team is fully dedicated to the Atlassian stack and can offer you peace of mind by managing, supporting, and maintaining your Atlassian tools. This allows you to maximize the benefits of your Atlassian applications and empowers your team focus on what they do best. Working with our Managed Services team offers you expertise and best practices that draw from our wealth of experience and from 15 years working with the tools. We take the maintenance process off your plate, making sure that your tools–and your team–run at peak performance.

If you're ready to hand upgrades off to our experts, get it touch with our team to learn more about our Managed Services offering.

 

 

Topics: managed-services upgrade atlassian-products
5 min read

What's Next-Gen Projects in Jira Cloud and When to Use It

By Amanda Babb on Aug 28, 2020 9:30:00 AM

Benefits of Next-Gen projects

NOTE: Jira next-gen projects are now named team-managed projects, although all the valuable features that have made them an indispensable tool for managing your team's work for years remain the same.

Atlassian has always held the concept of the team in high regard. As you may know, even their stock ticker is TEAM. And with many organizations pushing to Atlassian Cloud from their Server or Data Center solutions, it's no wonder Atlassian is removing barriers to entry for first-time users and admins. Whether you choose Standard or Premium, Jira Software adds the ability to create next-gen projects.

What is a next-gen project? 

Jira Software next-gen projects are a simple and flexible way to get your teams working. With some limited delegated administration, next-gen projects are created using a pre-defined template (Kanban or Scrum). These projects also come with three pre-defined roles: Administrator, Member, and Viewer.

  • Administrator: Updates project settings and can add other Administrators
  • Member: Can perform most functions such as create, edit, assign, and transition issues
  • Viewer: Can view and comment only

By default, if a user is added to the Jira Cloud site and provided access to Jira Software, they automatically become a member of every next-gen project (also known as Open). However, a next-gen admin can change the settings to be either Limited or Private. Limited puts all users of Jira software into the Viewer role and Private requires the admin to add a user to perform actions in the project. In addition, setting the project to Private hides the project from any search results. 

Each next-gen project operates similarly to a Classic Software project. You get either a Kanban or Scrum Board based on your project template as well as the reports you've come to know and love from the Server and Data Center products. One key difference is the addition of a Roadmap. Each next-gen project and board comes with a Roadmap. This allows teams to track start and end dates of the epics and better communicate with their product owners and stakeholders. 

The benefits of a next-gen project

Next-gen projects are flexible and delegate administration to the Administrators. This means the Administrator can create new Issue Types and Workflows, add unique fields, assign access to individuals or groups, and can enable or disable specific agile features such as enabling backlogs. This provides the ultimate flexibility for newly formed agile teams to work out their processes and data needs while performing their daily work. Let's take a closer look at each of these elements. 

Issue Types can be created on the fly at any time. As an Administrator, you can add up to 30 unique issue types to your next-gen project. By default, next-gen projects come with Epics, Stories, Bugs, Tasks, and Subtasks. If you remember, these are arranged in a loose hierarchy with Epics at the top; Stories, Bugs, and Tasks in the middle; and Subtasks on the bottom. Currently, any additional issue types will be added at the same level as Stories, Bugs and Tasks. If you'd like to add your own Subtasks or parent issues, feel free to submit feedback to Atlassian. 

Workflows are configured directly on your Board. Simply add a column to add a status to your workflow. That's it. You may also add rules such as assigning an issue or updating a field. Other Marketplace Apps can add automation triggers and the like to next-gen projects as well. 

Administrators can also add Custom Fields for your project. While Jira already comes with a robust set of Jira-created fields, you may choose to add checkboxes, people fields, numbers, dates, dropdowns and more. You can even change the order of the fields on the issue view to put the most important information at the top. 

Notifications on certain events can also be tuned to suit the team's need. For those already familiar with notifications, these events include: Issue Created, Issue Updated, Issue Assigned, Issue Deleted, etc. In a next-gen project, you can notify All Watchers, Current Assignee, Current User, Reporter, or a Project Role. Simply select the event and the people you'd like to notify, and Jira will take care of the rest. 

Last, but not least, there are nine separate Board features you may choose to enable for your next-gen project. This includes things like the Roadmap, Reports, Backlogs for Kanban, and more. 

There's no doubt that next-gen projects provide your team the ultimate flexibility in managing their work. With easily navigable menus and a simplified Administration interface, next-gen projects can be great for you and your team. 

The disadvantages of a next-gen project

One of the things we love about the Atlassian products is that they are super flexible and you can do pretty much anything you'd like with them. One of the things we hate about the Atlassian products is that they are super flexible and you can do pretty much anything you'd like with them. The same is true of next-gen projects. With ultimate flexibility and delegated administration, it becomes difficult to aggregate data across multiple projects. As a product manager, project manager, Release Train Engineer, or other person over several teams, you may find next-gen projects frustrating. 

Because the configuration of a next-gen project is unique to the individual project, gathering a status update is difficult. Not impossible, but you need a solid working knowledge of Jira Query Language (JQL) and good discipline from your teams to ensure they're transitioning tickets through the workflow. Creating custom Filters and Dashboards is your only way to aggregate data across projects. In addition, since each team can create their own custom fields, you risk data bloat. For example, one team may create a field called Bug Type using a dropdown and another may create Bug Type using checkboxes. While both are correct, to understand where Bugs are located, you have to add both fields to your filter. And the values may be unique per project as well. 

Work can only be estimated in Story Points, regardless if your project is Kanban or Scrum. This is also regardless of Issue Type. If you enable estimation on either a Scrum or Kanban next-gen project, every piece of work should be estimated and estimated in Story Points. Tasks, Bugs, and Stories all need points to establish a consistent velocity for predictability. 

Since there is a single workflow for all Issue Types, the team cannot split processes between types of work. If a Task follows a simplified process (To Do, In Progress, and Done), but a Story needs more detail (Backlog, Selected for Development, In Progress, and Done), the team cannot split these items into two distinct workflows. Every type of work must follow the same path through the board. 

There are additional technical considerations as well for things like Cloud merges (bringing two instances together) and Cloud to Server or Data Center migrations (moving off Atlassian Cloud to an On Premise solution). While these efforts are few and far between, all next-gen projects must be converted to Classic projects before these efforts start. 

Are next-gen projects right for you? 

At Praecipio Consulting, we believe you must use the right tool for the right job. The same goes for next-gen projects. While there are many benefits, there are disadvantages as well. How do you manage cross-team dependencies? Are you willing to span multiple projects for status updates? Do you trust your teams to make the most out of the functionality? Are there long-term scaling opportunities you need to consider, such as integrations, or other products, such as Advanced Roadmaps, for Jira or Jira Align? If you'd like to know more about next-gen versus classic Jira Software projects, Praecipio Consulting has extensive experience managing and assisting clients with these questions and more. 

 

Topics: best-practices business-teams cloud atlassian-products jira-align next-gen-project
1 min read

Atlassian Hosting: What are my options?

By Morgan Folsom on Aug 20, 2020 2:15:00 PM

Atlassian Hosting options

One of the most important decisions that your organization has to make with regards to your Atlassian applications is which hosting option you'll use. Not only will you will want to review the differences between Cloud, Server, and Data Center, but unless you are using Atlassian's Cloud platform, you'll also have to make key decisions about infrastructure. Praecipio Consulting offers Cumulus Cloud, our managed hosting solution to help make your decision easier. 

Amanda Babb, our Principal Consultant, was recently invited to chat with the hosts of “CarahCast,” Carahsoft’s new podcast dedicated to bringing listeners the latest in Government IT case studies, technology trends, recent legislation news, and Government IT best practices. 

In the podcast episode titled “Hosting in the Cloud with Atlassian,” Amanda discusses Cumulus Cloud, our comprehensive hosting solution that manages server and data center editions of the Atlassian suite, the value it brings to the enterprise organization, and why it's different from any of the other solutions out there.

Listen to Principal Consultant Amanda Babb outline all of the above and more in this Atlassian Podcast with our partner, Carahsoft. 

Topics: atlassian blog migrations cloud hosting atlassian-products podcast
4 min read

Enterprise Service Management Blog Series (Part 1): Why ESM Is Hardly A New Concept

By Praecipio Consulting on Jul 22, 2020 12:45:00 PM

2020 Blogposts_What is Enterprise Service Management

Michael Porter, a former Harvard professor, is one of the founding fathers of business strategy. He lent credence to the field by developing several ideas, frameworks, and theories around strategy that have been utilized, debated, and taught for four decades now. You may be familiar with his 5 Forces model, which is used to analyze the competitive landscape of a given industry, or his course titled “Competition and Strategy”, a requirement for all first-year Harvard MBAs. Though his ideas and theories are certainly not perfect and have evolved over the years, they laid the groundwork for modern businesses to think about their strategy, their position in the market, and their ability to move forward.

And when you think about it, it’s weird that some consider Enterprise Service Management to be a new business process management trend. Let me explain. 

In 1985, Porter co-authored an article with Victor E. Millar in the Harvard Business Review titled “How Information Gives You Competitive Advantage”. In it, he laid out a central argument that said with the explosion of computer usage, companies would have access to a ton of information, flowing freely through the organization, that would allow managers to make more informed decisions faster. This, Porter argued, would fundamentally change how business was done and provide new ways for companies to stay ahead of their competitors. 

Consider this excerpt from Porter’s article:

“The value a company creates is measured by the amount that buyers are willing to pay for a product or service. A business is profitable if the value it creates exceeds the cost of performing the value activities. To gain competitive advantage over its rivals, a company must either perform these activities at a lower cost or perform them in a way that leads to differentiation and a premium price (more value).”

In other words, to gain an advantage over competitors, companies must perform their value activities at a lower cost or in a way that adds more value. Porter foresaw the drastic increase of information that would be available to businesses with the shepherding of the digital era. He logically concluded that such information, if used and communicated correctly, could be advantageous to managers looking to make decisions around the value-added activities in which their business engages.

The prediction of a sharp increase in the amount of information has certainly come true. In the era of big data, companies gather, store, process, and use more data than ever before. The problem is that typically this information is siloed, only about one particular subject, or only accessible and understandable to a few highly-skilled workers. This is the problem that enterprise service management will solve to bring Porter’s 35-year-old vision to fruition once and for all.

Enterprise Service Management (ESM) holds that the (mostly digital) processes that have been championed and used to gain efficiencies by IT teams for so long apply to the business as a whole, as seen by the adoption of similar processes and technologies in departments like HR, Facilities, and Procurement. ESM suggests that an organization should have a tool, which typically takes the form of a piece of software, that allows information to flow easily, quickly, and freely through the organization (sound familiar?). At Praecipio Consulting we have grown fond of referring to this as an operating system for business - one central piece of software that is used nearly ubiquitously in the organization, one that allows work to flow from division to division, team to team, teammate to teammate, with no loss of information and an attached, rich history.

Consider the typical lifecycle of the development of a new offering by a business - whether that be a software feature, physical product, or a new service offering. Marketing will research the market and determine where gains can be made. They will pass intel along to Product, which will develop these insights into a new product idea. The Product team will work with Development to create requirements, Dev will build it, QA will test it, and then it will be released to the market. Along the way, Marketing will generate buzz, Sales will sell, Legal will validate legality, HR will manage employees working on the offering, so on and so forth. In short - it takes a village, a coordinated effort among teams from different parts of the organization to deliver the new offering to market. 

The logic of a single system which transmits work in this lifecycle with no loss of info and rich history is apparent, as is the cost savings garnered from a single license paid to a single vendor, maintenance and training for one system instead of several, and usage of an efficient process unmarred by clunky handoffs to other systems.

To achieve this business process nirvana, we have long advocated for the usage of Atlassian’s Jira, Jira Service Management, and Confluence products. Similar to Apple, Atlassian set out to develop products that work together seamlessly, but unlike Apple, Atlassian has retained that characteristic and further developed it to the point that these three products work together in harmony. The malleable and flexible nature of these products has helped them evolve from those used exclusively by software development teams for bug tracking to those used by IT, HR, Legal, Marketing, Customer Service, and several other business units. The ability of these products to merge these disparate units within a business shows an exciting step forward and potentially a culmination in Porter’s vision of a connected and integrated business.

In the next articles that will form part of this ESM blog series, we will further explore the logic and numbers behind enterprise service management, and why and how it can help your company. 

Topics: blog best-practices enterprise service-management atlassian-products jira-service-management frameworks
4 min read

How and When to Choose the Right Atlassian Solution Partner

By Christian Lane on Jun 18, 2020 11:44:49 AM

2020 Blogposts_How and When to Chose the Right Atlassian Partner Support

No matter the size of the organization, small business or Fortune 50, most successful companies will come to a point where they need a technology and business solution partner to optimize processes and move projects forward. 

In today's disruptive business world, you may have furloughed employees or lack resources for critical functions. There may be no better time to hire an Atlassian Platinum solution partner, especially if you can’t afford the project to be fumbled. 

However, choosing the right partner can be difficult. All vendors claim to be the best, have impressive client lists, and work with smart people. Where should you start?

First, understand the consequences of a poor decision. Lost opportunity costs, money wasted, boss disappointment, ruined long-term growth, damaged reputation, and careers devastated - maybe even yours. Scary thoughts, indeed. 

A much more pleasant exercise is to consider if the project goes well. If you use company resources well and with a good result, you could be seen as the rising star and be assigned more complex and important projects. With this recognition comes upward career mobility, peer respect,...and a raise!

Make sure these factors are part of your Atlassian partner selection process.

Research 

Your solution partner is happy to tell you about their successful projects, but after they give you their initial pitch, ask some hard questions such as, “What is your Net Promoter Score (NPS)?” NPS is a widely accepted measurement of customer satisfaction and woven into the culture of companies that take the customer experience seriously. The higher the score, the more satisfied the customer is. If they don’t know what NPS is, or they don’t track it, it gives you a good glimpse into their business practices. You will find that companies with a good NPS, want to let you know about it early in the process. Christian LanePraecipio Consulting founder says, “It’s one of the first things we communicate to soon-to-be clients. We want them to know that with an NPS score of 70, they are in good hands, especially since the IT consulting industry average is 31. Setting high expectations for our sales and delivery teams ensures we focus on customer success and continual improvement to our delivery model. This helps earn trust so we can talk next about speed, execution, and value.”

 christian-lane

Other good questions to ask are: 

  • Tell me about your change order volume as a percentage of overall revenue.
  • What is your change control revenue as a percentage of overall revenue? 
  • If something goes wrong in the client relationship, what is a typical reason?
  • What does the discovery process look like?

The method

Be sure to ask about their methods and how they execute during an engagement. IT projects can be complex, and it takes a focused effort from the solution partner and the client to get a good result. Ask about how both teams will stay on track and what the regular cadence of communication is. Do they have a method that marches you toward success? Or do they rely on you to assign tasks? Ask them what quality controls they have in place so that no detail goes unnoticed. Lane’s best advice? “Get a comfort level with reliability and consistency.”

Great partners sell solutions, not just blocks of hours. 

Consultants or operators

No one solution partner has a monopoly on the smartest people, so don’t let the number of certified Atlassian engineers be your sole decision driver. What’s more important is how the talent communicates. Do they simply fix your problems and wait for the next one? Or do they take a more consultative approach and advise on things like, how your projects will connect to your existing infrastructure or the cost-benefit of creating features. Lane summarizes it best when he says, “Consultants help you look through the windshield and see where you are going.”

Ease to do business 

Some operators keep a minimal US team and outsource across the world. This could be problematic due to the differences in time zones slowing down the work, or having a language barrier that requires more middlemen. “It’s an opportunity for error,” Lane says. Don’t let your project be the one that they use to get through a learning curve. All of these factors contribute to how easy it is to do business with the solution partner. 

Getting complex projects off the ground or stalled projects across the finish line is hard enough to do even with the right solution partner. Failing to spend enough time and energy on the vendor selection process can have catastrophic results with major repercussions. However, choosing the right solution partner can get you recognition and bring the rewards that a superstar deserves.

Read more about the different tiers of service here.

Topics: atlassian blog culture atlassian-products nps atlassian-solution-partner
3 min read

Are Atlassian Tools Right For My Business?

By Brian Nye on Jun 3, 2020 12:15:00 PM

2020 Blogposts_Statuspage copy

Many businesses considering or have purchased one or more products from the Atlassian stack (Jira, Confluence, Bitbucket, etc.) have thought, "Is this right for us?" If you are asking this question, you are not alone. Some question why a business would invest in tools that they are not even sure if they meet their business needs, and this is rooted in the fact that Atlassian tools are extremely flexible, perhaps too flexible. Combine Atlassian's flexibility with evolving process requirements and lack of true Atlassian expertise, and you get a toolset that doesn't fit your business needs. This doesn't need to be your reality. You just need some guidance, and Praecipio Consulting can help by doing an Atlassian Process Assessment.

What is an Atlassian Process Assessment?

Praecipio Consulting understands two things extremely well: business processes and Atlassian tools. Simply put, the Atlassian Process Assessment utilizes our core competencies to understand your business process challenges to put together a plan of action on how to get you on the right path to maximize the Atlassian technology stack. It doesn't matter if you are brand new to Atlassian or a long-time user, we can help you figure out the best approach for implementing the products. Here are some of the cases we have encountered during the last year. 

  • One business was in the process of transitioning from another tool to Jira. They were looking to use Aha! as their product roadmap tool but wanted to use Jira for their development teams. We helped them align Jira and Aha! from a process perspective, and we figured out how to structure Jira to support their agile development needs. 
  • A company was undergoing a merger, where two instances of Jira and Confluence were going to be used in a single instance. The entities that were merging used the tools differently based on their users' needs. They brought us in to figure out the best way to structure Jira in the new shared instance and also to correct years of system misuse. We provided a roadmap detailing out the order of operation needed to be successful in their efforts for simplifying and streamlining processes. 
  • One client had been using Jira and Confluence for many years to manage various teams, and they were wanting to see a more holistic, SAFe view of their work using the Atlassian stack. During the assessment, we evaluated not only their use of Jira and Confluence but also their SAFe implementation by identifying areas of opportunity for key agile practices. 

What to expect during an assessment

Praecipio Consulting conducts the assessments by meeting with various teams to discuss their overall business processes and what tools they currently use to support them. Typically, we interview small groups of people in similar roles (such as Scrum Masters or Program Managers) who have a comprehensive understanding of their current processes. We look for patterns of common challenges that teams across the organization are experiencing and result in inefficiencies. Once the patterns emerge, we propose recommendations about how to overcome those challenges and how to best represent the process in the tools. These recommendations are prioritized into an implementation roadmap so clients know how to go about making the changes in their organization. 

Throughout the assessment, the client's project sponsors gain valuable insights into how the business performs and the areas that the Atlassian stack can help make processes more efficient. Praecipio Consulting takes as many voices as possible into account so that we can get a "big picture" understanding of the good and the bad. That way we can give our expert take on what we should do going forward. We have seen hundreds of tool implementations across different industries, which allows us to confidently give you the best advice for making impactful changes to your organization.

What clients say about our Atlassian Process Assessments

After all of our engagements, a retrospective is held for the client to express the value they received from the Atlassian Process Assessment. Here are just a few of the things our clients have found valuable about the service:

  • A healthcare technology company said, "It was a positive interaction that presented a clear vision of what we want to do after the engagement so we can be tactical about our long-term strategy."
  • A telecom device manufacturer stated, "The consultant was able to navigate the personal nuances of our teams and provided us with great value that helped us move forward in our transformation."
  • An energy provider said, "We needed to take a step back to look at what we were doing and come up with a strategic roadmap. The consultant helped us understand the gaps in the path and charted a course that's in line with our practices so we are not trying to learn those ourselves. It was a good investment in what we need to do."

Are you ready to let our professionals take a look at your business? Our fresh set of eyes can provide you with new insights and guidance towards a more healthy and productive Atlassian implementation. Reach out to our team if you are interested in an Atlassian Process assessment!

Topics: blog process-improvement tools process-assessment atlassian-products
4 min read

How To Run D&D Campaigns With Trello

By Luis Machado on May 29, 2020 12:45:00 PM

2020 Blogposts_How Jira helps your team work remotely copy 3

It’s 2020, and the reality for a lot of folks has seemingly changed overnight. Working from home, remote meetings, a whole slew of new tools to learn and master. It’s a strange new world, and not just for our professional lives but our personal lives as well. So how do we make the change? How can we adapt to this new frontier?

I’ve been playing games with friends on the internet for several years now, way before social distancing practices became the norm. Even though we live hundreds of miles apart, I can still lead a group of close friends through the dark, dangerous lairs and pitting them against frightening creatures, all for glory and the pursuit of the almighty gold coin. There are a plethora of tools available that allow people to play tabletop games without the table, such as Roll 20, D&D Beyond, Discord, Skype, among several others. But there is a distinct lack of tools available for the person running the game, the game master, the dungeon master, the decider of fates, and facilitator of adventure to keep it all organized.  

When running a game there is A LOT to keep track of: monsters, treasure, characters, towns, plot points. If you’re using an old school pen and paper, you’re going to need a mighty large binder. Naturally, the desire to digitize this content has led to some creative methodologies. The one that has stuck with me is using a site that falls right within my wheelhouse: Trello.

At its core, Trello is a tool that helps you manage lists for collaboration. You create a list and then populate it with cards. The title of the card shows up in the list, clicking on the card lets you see an expanded view with more detail. You can also add custom labels to create color codes.

I first came across this idea from a post on Reddit called "DMing with Trello". This method gives you easy access to a board for the DM (as in Dungeon Master!) screen to have frequently referenced rules and definitions handy, a way for tracking combat, and board for managing campaign-specific content.

Campaign Content

dd1

While I'll breakdown how I manage my campaigns, how you organize your lists can vary. I started with making a list for the town Daggerford, where the players interact with each other. Each special location within the town has is its own Trello card. These locations, like a blacksmith, inn, or tavern can be listed for easy reference and the numbers in my list correspond to locations indicated on a map. The use of the built-in labels lets you categorize cards within a list, and the sorting view lets you filter the list with a specific category. So, if I’m looking for just blacksmiths, for example, I can filter the list for just that category.

dd2

dd3

Clicking on one of the cards brings up a larger, more detailed view where you can keep your notes.

dd4

Cards can also be formatted using markup to let you get as fancy as you want.  You can also extend functionality if you’re using Google Chrome by installing a browser extension: Trello Card Optimizer.

dd5

Combat Tracker

dd6

The combat tracker is a series of lists. The first list is where I set the turn order (top to bottom). Each subsequent list is a round of combat, numbered accordingly, and the players and monsters are all cards. You can arrange them all in turn order and then advance them to the next round when it’s their turn by clicking on them and dragging them to the next list. 

Keeping track of combat can be particularly tricky in an online situation. Using Trello gives you an easy, straightforward way to do it.  In this setting, I use the labels for various statuses and ailments. Poisoned by a snake? Petrified by a basilisk? There’s a label for that! Lastly, I keep a card or two at the top of the initiative list for easy access to the music links I use.

DM Screen

dd7

Last, but not least, is the DM screen. Set up in a similar manner to the campaign content, this board offers you the ability to quickly reference game rules that you frequently have to look up. How does grapple work again? What happens when a character is blinded? All these questions and more can be answered here, and you don’t have to worry about accidentally bending or tearing your rule book between sessions.

The DM screen is available as a public board that you can copy to your own account, allowing you to customize it to suit your game. I highly recommend using the Trello Card Optimizer with Chrome because it adds a lot of visual organization to your cards and board. 

Now get out there (and by "out there", I mean exploring the world of Trello from your home), and take a shot at organizing your game. As a final note, when the time comes to reunite with your players for an in-person session, you can travel light with just a laptop and have all your hard work available at your fingertips.

For more information on Trello and the Atlassian suite of products, reach out to your favorite Dungeon Master...er...Platinum Solutions Partner. Happy gaming!

 

 

Topics: collaboration project-management trello atlassian-products
3 min read

How to Make State Business Services Better, with Automation by Atlassian

By Atlassian on May 28, 2020 5:31:07 PM

Moving through processes faster, improving service responses, and reducing unnecessary workloads are three great ways to make state business services better, less costly and more efficient. Digital project management, service desk, and knowledge management tools can provide these benefits and more with powerful yet easy to use automation features. Here are 3 ways that the Business Services Division of Secretary of State departments can use automation to improve job satisfaction, reduce costs, and at the same time boost the state’s economic development, with Atlassian solutions.

At Atlassian, we help teams of all shapes and sizes work better and more efficiently with an integrated and comprehensive set of tools, services, and playbooks. For this example, we will look at the automation capabilities within three of our tools: Jira Core, Jira Software, and Confluence.

Make Workflows Move Faster with Jira Core

Jira Core is designed for managing projects and keeping teams organized. Workflows are one of its most powerful features. From simple to complex, you define the workflows to match your process, tasks, and tracking needs. As tasks move through the workflow, built-in automation makes the process faster and easier. For example, you can have new business license applications automatically routed and assigned to the appropriate team member based on current workload, expertise, or any other criteria. Make things simpler and reduce confusion by hiding fields that are not necessary for the current application or status. Modify field permissions and restrictions to ensure the right people act on the right things at the right times. Or generate automatic email notifications to key stakeholders when applications change status, including external addresses such as the person who submitted it. By automating workflows, you spend less time on administrative tasks and more time on strategic ones.

Create Automatic Reminders for Open Issues with Jira Service Desk

Jira Service Desk is ideal for delivering exceptional services, and issue tracking is a core component. You can see and collaboratively resolve issues based on your defined set of priorities. Sometimes your team gets really busy, perhaps with an unusual flood of queries or new applications, causing them to overlook a few open issues. In a manual world, these slipups may not come to light until a detailed status review meeting or the originator complains, negatively impacting service targets and satisfaction ratings. Automating reminders eliminates this risk. For each different status you can easily specify how long an issue can remain unchanged before a notification is sent, in minutes, hours, or days. This simple trick keeps things flowing and ensures that the team processes issues in the proper order and timeframe. It also serves as the baseline for some pretty great team performance analytics.

Use Page Templates to Improve Operations with Confluence

Confluence provides a team workspace for collaborating and organizing work. Confluence page templates are essential building blocks for reducing duplication and enhancing compliance. There are many ways to choose templates, whether provided by Atlassian right out-of-the-box, available from our extensive marketplace, or created for your specific needs. Staff get a jump start on their work by using a template instead of starting from a blank entry. For example, a meeting notes template starts things off quickly by automatically bringing forward open action items. Add your agenda, record discussions and decisions during the meeting, and update action items as they are worked on. These are a tremendous boost for remote or distributed teams, too. Teams collaborate more easily and stay on the same page at the same time—with each team member seeing the updates in real-time. Team members each have their own to-do lists generated from these and other meeting notes, giving them a complete and up-to-date view of what they need to work on.

Automation makes things work faster, improves response times, and results in higher job satisfaction. State business services departments can leverage Atlassian’s powerful, easy-touse automation to enhance productivity, respond faster, and help fuel their state’s economic development.

Topics: jira atlassian blog automation confluence government project-management atlassian-products
2 min read

How Jira Can Help Your Teams Work Remotely

By Michael Knight on May 8, 2020 9:15:00 AM

According to a recent article published in the Harvard Business Review, one of the common challenges when working from home is a lack of access to information. At Praecipio Consulting, we often see this challenge with many teams, especially they remotely. Here's how Jira can help:

Visualize current work with Kanban boards

A Kanban board (or a similar variant) can be a remote team’s best friend. Instead of emailing, Slacking, texting, or calling a coworker to find out the status of a particular work item, a team member can simply navigate to the Kanban board and find a wealth of information. A well-configured board is easy to read and quickly conveys a brief description of each item the team is currently working on, as well as the status, assignee, and any other team-specific information. This helps cut down on extraneous communications within your organization and provides remote workers with a quicker and easier way to access information.

Reduce the number of emails by commenting on issues

Not only is commenting on issues quicker than typing up an email, but comments also live in publicly visible space and are saved in the issue. This immediately creates two advantages over email. First, commenting makes it much easier for other coworkers to see the progress on the issue, preventing them from having to send an email to ask questions about the issue, who’s working on it, when was it last worked on, and what progress has been made in the past week. Second, users never have to wonder why somebody made a particular decision or repeatedly ask for information because the entire conversation is stored within the issue. Using @ mentions to tag a coworker or manager helps speed up this process and better organize the information, in addition to drawing specific users to the issue and providing context.

Benefit from linking Jira and Confluence together

When Jira and Confluence are linked together, one can simply enter a Jira issue key into a Confluence page, and it will automatically contain a link to the Jira issue. Similarly, it becomes possible to link a Confluence page to a Jira issue by just referencing the title of the page. A few common use cases include: linking a resolution document in Confluence to the incident issue in Jira, displaying the progress of related Jira issues on a requirements document in Confluence, and linking several helpful articles to a service request in Jira. This helps solve similar problems more quickly, reduces time spent searching for that one Confluence article, and eliminates the need for status emails.

Jira was created to help teammates access information, allowing them to visualize and organize complex and hard-to-see work; and that's why Jira is the perfect tool for a remote team.  

 

Struggling with remote work in this time of uncertainty? Praecipio Consulting provides a turnkey implementation of best practices in Jira with an Accelerator. Whether you're supporting SDLC, ITSM, or PPM, we can rapidly deploy Jira to support your team. Reach out to us to learn more about Jira and how it can facilitate remote work. 

Topics: jira blog teams tips collaboration atlassian-products work-from-home remote-work
4 min read

Jira: Your Path to Digital Transformation

By Brian Nye on Mar 2, 2020 2:00:00 PM

JiraYourPathtoDigitalTransformation-1

We're all Going Digital

No matter the industry or product, digital transformations are happening all around us. Gone are the days where a product is just a product. It's now a mechanism that gives us analytics and prepares us to launch the next best thing. Everything we touch has some digital aspect to it, and companies that never planned on competing in the digital arena are needing to catch up to the standards of today's landscape. 

I'm sure that many of you who have been in business for more than 10 years, working in sectors that seemed to have no digital relevance, but now are investing for a digitized future, whether it's through:

  • Augmented reality to see how a product would look on you
  • Drones delivering packages from purchases made by a scan of your face.

The digital age is firing up, and the question is, are you STILL using a spreadsheet to manage your business? 

Running a Business Like it's 1999

I loved a powerful formula and a well-crafted spreadsheet. Everyone has that one colleague who is a macro wizard at pulling together all the data and using it to plan the future of your products (that was once my job).

Think about running a multi-million dollar business from a spreadsheet that: 

  • Is locked for editing
  • Is never up-to-date
  • Is passed around in several emails
  • No one has the same version of

Some of you don't have to imagine; it's your reality. More than once, production slips, and you've missed hitting your target shipments because the business didn't have the most up-to-date information. 

I have personally seen this over and over again during my five-year tenure at Praecipio Consulting, and it comes down to two issues: 

  1. The business is stuck doing things the old way. 
  2. The tools are just as old as the processes they are supporting. 

And on top of all that, there's an overall demand and expectation to be more innovative than ever. Naturally, we start to silo the business into segments so the "core business" can keep marching to the same tired beat while the digital team is building a platform that's state-of-the-art. 

How do we close the expanding gap between a growing machine and a time machine? 

How can we plan for when Ralph is out, and no one can get to the spreadsheet with the latest numbers?

Digital Transformation Doesn't Happen on a Spreadsheet 

To transform, you have to make significant changes. The tried and true spreadsheet can't keep up with the on-demand visibility needed in the digital environment. Granted, it's a useful tool and has a place in business, but it shouldn't be the source of truth for guiding your business down the path of digital transformation.

The same applies to using email as a tool to operate your business and for project management. Not only can managing hundreds of incoming emails be counterproductive, but email is not a platform built for collaboration, nor can it provide the visibility needed to compete in the digital landscape. 

Jira, on the other hand, is designed to handle this task for the business. Gone are the days when Jira is just a "developers tool." It's now being used as the primary source of understanding in all facets of business and helping leaders make real-time decisions about what comes next on their product and operations journey.

Most development teams are already using Jira to plan, track, and report on the requirements determined by the business. However, the business side of an organization is hesitant to adopt the same tool as the development teams. Centralizing all the data and processes across all aspects of your business using the Jira platform  can help your teams better understand where your business is going and, better yet, why it is where it is. 

I can't count the number of times when I've heard of innovative teams needing to pull data out of reports and update an outdated spreadsheet because there is a perception that the business finds Jira too hard to use or reference. 

Becoming a Digital Transformation(ist)

Business leaders, it's time to step up and utilize a toolset that bridges the gap between where you are and where it's all going. If you have an OKR around digital transformation and you're still using a spreadsheet to plan when you have Jira in your business, you are 0% complete on that objective. 

The good news is that you can change your business, and Jira isn't hard to learn; you just need some guidance on the transformation. 

At Praecipio Consulting, we have helped hundreds of clients, big and small, build business processes in Jira to support their needs and become a digital transformation(ist). The first step is understanding you have a spreadsheet problem, and once you own that, we can help you build a better business. 

 

Topics: jira best-practices digital-transformation atlassian-products
3 min read

How to Plan & Track OKRs With Atlassian Tools

By Brian Nye on Feb 5, 2020 9:39:41 AM

OKR: More Than Just a Buzzword

Like most of you, I have been challenged to establish my annual "OKRs" at the start of this new year. It seems that OKR has suddenly become a big buzzword that businesses have been throwing around the past few years. If you were like me before ever hearing of this acronym, you might be asking yourself: what is OKR, and what happened to the classics like KPI or SMART goals?

I decided to do some digging around to understand where this new buzzword comes from, and I learned that the term, in fact, has been around quite some time. More than 30 years to be exact! OKR was first introduced in the book High Output Management by Andy Grove, which was published in 1983. This term would later be used by one of Google's early investors, John Doerr, who used to work at Intel, and then it caught on at Spotify, Amazon and other big companies. That's when it gained traction to become the business buzzword that it is today. 

What is OKR?

Enough with the history lesson, what is exactly is OKR?

Simply put, OKR is a strategic framework that stands for (O)Objectives and (K)Key (R)Results. When setting your OKRs, the Objectives should be tied back to your organization's mission, vision, and strategic initiatives, and the Key Results are the measurable components that help you determine whether or not you are meeting your objectives. 

So, what is the difference between OKRs and KPIs or SMART goals? To start with, KPIs are are just measurements that represent output and don't tell you the entire story, whereas OKRs give you the big picture from the start to finish. SMART (Specific, Measurable, Achievable, Relevant, and Time-bound) goals are usually a bit more targeted and lack the full scope of the OKR methodology. You can think of OKRs as a collection of SMART goals and their respective KPIs. 

Plan & Track Your OKRs with Atlassian

Now that we understand the concept of OKRs, our next step is to establish them, and there is no better tool for this process than Confluence. At Praecipio Consulting, we dedicated a Confluence Space to our OKRs because we wanted to make sure that it is easily accessible to our employees. After all, we are all working together towards the same strategic objectives, and Confluence is the perfect collaborative space that allows us to check in on our goals and progress at any time. 

We started by organizing our OKRs by year so that we know what we have achieved in the past, as well as what we are working towards now and into the future. Within each year, we group our OKRs into overarching concepts that we refer to as "tracks". For example, we have a track for our 2020 OKR around "Climate Action Plan", and we use the Confluence Project Poster blueprint as a guide to document why this is part of our strategic objectives and who should be involved.

This also serves as a snapshot to get people excited about a track's children pages, which are the actual OKRs. Our OKR pages are custom templates that we built out and allow us to describe how we want our OKRs to look. More importantly, we use the page property macro to capture key pieces of information to display on that specific year's parent page, and we utilize labels that make the pages easier to reference.

For instance, one of the OKRs is to involve you, our community, by educating you and inviting you to join our efforts in overcoming climate change, which we do by providing your with content and information about organizations that we partner with via blog posts and webinars.  We will measure our success by the content we produce, the number clicks we receive on that content and the success stories shared by you as a result. 

To help with following up on OKRs, we utilize a Jira project for internal projects to track each OKR as an Epic and all the separate tasks as related issues. We use a Fix Versions as a grouping mechanism for the track so that we have visibility on how we are doing from a big picture perspective. 

Improve Your Goal-Setting Process

OKRs are not new to the business scene, but they can definitely help drive business value and help you reach your strategic objectives. Confluence is a great tool that allows you to capture the "why" and "what" you want to do, and Jira can show you "who" and "how" the OKR is doing.

If you are interested in learning how Atlassian tools can help you with your goal-setting and other business processes, contact us at Praecipio Consulting, and we'll be glad to get you on the right "track". 

Topics: jira praecipio-consulting confluence process-improvement global-climate-crisis atlassian-products
4 min read

Importance of Jira Resolutions

By Brian Nye on Jan 28, 2020 1:30:00 PM

One of the most frequent questions we get asked when on a project is, "Why do I need 'Resolutions', can't we just use statuses?" The short answer is "No" and it's because they are not the same thing. I know that you all would be terribly disappointed if I just stopped here so I'm going to outline a few reasons why it's an important field and share some best practices. 

Why Do I Need the "Resolution" Field?

The Resolution field provides a few important functions to issues in Jira:

  1. When it's set, the issue key will be displayed as a strikethrough (KEY-556), which is extremely helpful when looking at linked issues in the issue navigator or other areas where the Resolution field is not displayed. 
  2. It's the field that Jira uses for the "Created vs. Resolved" report. 
  3. It's what the 'system filters' and 'gadgets' use to determine if the issue is resolved, not the statuses. 
  4. Lastly, it's the field that sets the "Resolution Date", which is a great way to know when something was completed.

For these reasons, you are doing a disservice to your organization by not using the Resolution field. Next I'm going to talk about some common mistakes that people make and how to correct them. 

Common Mistake 1: The Issue's Status is the Same Thing

While you may have created a status that reflects the same intent of the Resolution field, it's not considered to be best practice. Think about having to search every status to determine all the issues that were closed. It would be tragic if you were to forget one of them and it would be difficult to standardize around them as Jira Admins can add statuses as they see fit. Not to mention, issue statuses do not have an out-of-the-box way of knowing when something enters into that status. In reality, it's much easier to think of the lifecycle of the issue when it comes to issue statuses. If the issue is at the end of it's lifecycle, choose a status name that reflects that no more work is going to be done (I have a preference for the word "Closed" as it's neutral in meaning and conveys we're not going to be doing anything more to the issue). The Resolution field can then be used to differentiate why the issue is closed. This gives the resolution a purpose and helps people use the resolution correctly, giving the benefits described above.

Common Mistake 2: I Don't Want to Enter a Resolution

A conversation that starts like this is usually because the client doesn't care about defining the reason why an issue is closed, or they have a bunch of resolutions in the system because of poor decisions made by Jira Admins. There is one main question that needs to be asked to decide what needs to be done - "Do you always want the resolution to be the same when transitioning to this status?" If the answer is "yes", use a post function to set the Resolution to a single resolution. This will achieve the goal of setting the resolution without asking the user. If the answer is "no", then you may want to limit the available resolutions to the user. You can do one of two things:

  1. Delete some of the resolutions in the system. 
  2. Limit the options available on the transition by using a workflow property. 

If you decide to delete resolutions, you will be changing data for issues that have that resolution. This means you are impacting the Jira instance and may want to warn everyone before making the change. Jira won't allow you to make the change without giving a new value for the issues impacted by deleting the resolution. However, if you decide to use the workflow property, understand that this is on a workflow-by-workflow basis and will need to be instituted anywhere the change is needed. Additional information on workflow properties can be found here.

Common Mistake 3: The Dreaded "Unresolved" Resolution

I can't tell you how many times I've seen this and cringed. Here is the issue with adding an "Unresolved" resolution (other than being an oxymoron) when an issue is created, the Resolution is null, displaying "Unresolved" as the text on the ticket. What typically happens is someone will place the Resolution field on a Create or Edit screen. The Resolution field is always required when presented on a screen and since there isn't a resolution at this point, the user is forced to make a selection that doesn't apply. To fix this, a Jira Administrator will go in and create an "Unresolved" option to match the text displayed on the issue when no option has been selected. This is not the correct solution to this problem. This actually causes all sorts of data integrity issues and should be corrected immediately. Check out this Atlassian knowledge base article on ways to identify and correct this problem.

How to Use Jira More Effectively

Jira is a big complex tool that can be used in many different ways. This is just one seemingly important aspect that really can change the expected behavior of the application. We Praecipians have seen a lot of "interesting" uses of the tools and have helped guide many clients on how to use the tool to support their processes. If you are struggling with how to best use Jira for your organization, reach out! Praecipio Consulting offers Process Assessments that focus on your processes and your environment to ensure you are getting the most out of your Atlassian tools. 

Topics: jira blog best-practices tips atlassian-products
4 min read

Accessibility With Atlassian Products

By Amanda Babb on Dec 10, 2019 10:30:00 AM

Student Diversity is Key for Learning

Over the last two years, I've had the pleasure of partnering with Atlassian University to provide a wide range of training, including in-person courses, virtual courses, and even being the voice of Planning with Portfolio for Jira. If I had to count, I've likely delivered training to close to 1000 students since 2017 as an Atlassian Certified Instructor, but this week was a first – one of my students was blind. 

When teaching an Atlassian University course, we provide students with access to a virtual environment to practice the concepts presented. Each student is also provided soft copies of the slides as well as a lab workbook to guide them step-by-step through the environment. This particular course, Confluence Server Essentials, provides new users the opportunity to learn about the basics of Confluence. Navigation, page creation, blueprint usage, and collaboration features such as @ mentions, comments, and blogs are all covered in the full-day course. 

My blind student had a laptop with accessibility features and used the Jaws Screen Reader to help navigate the different UIs of the applications. He also had a colleague to assist him if needed. As I started the course, he was attentive and eagerly participated in the discussions. However, when it was time for everyone to log in to their environments and start the first set of exercises, I noticed that he was starting to fall behind. 

During the exercises, his assistant had a technical issue with her own laptop and asked if I would step in while she talked to tech support. I sat down and watched as he tried to navigate his screen reader through the Confluence System Dashboard and eventually to the correct Space to continue through the lab. This was my first time working with a screen reader, and I spent quite a bit of time wondering how it chose which parts of the screen to read. However, once we got into a rhythm, I was able to help him navigate to the correct menu. By the end of the time box, we managed to complete two of the four exercises. 

Accessibility in Atlassian Products

Atlassian supports or partially supports accessibility requirements for Jira, Confluence, and Bitbucket Server and Data Center products, in compliance with Section 508 and WCAG 2.0 (AA). At Praecipio Consulting, we developed a custom accessibility app for Jira, at a client's request, to accommodate sighted and non-sighted users. While support and partial support of accessibility are steps in the right direction, I still needed to find a better way to help this student. 

Enter the Atlassian Marketplace. If the functionality doesn't exist in the products themselves, we search the Marketplace for apps to add on to the instance. There are over 2000 apps available for Server, almost 1000 for Cloud, and nearly 700 for Data Center instances of the Atlassian applications, and these apps are generally tagged with additional information to further help you make the right choice. Through a quick search of all compatible apps tagged as Supported, I found two that looked promising: Accessibility for Confluence and Unstoppable for Confluence. Not knowing which one would work best, I tossed a coin. 

Because the Atlassian University lab environments work like a mini Server environment, they function the same as the customer instances of Confluence we work in every day. Following best practices, I wanted to test the installation of the app in a separate environment before installing it for the student. In my Instructor Environment, I found the user with the most administrative rights (as per the lab workbook) and installed the app. A quick check of the documentation told me the additional installation steps needed to activate it. As testing is important as well, I validated functionality myself first, and I was confident this app would provide the student with a better learning experience. 

A Retrospective on the Accessible Experience

Once installed and configured, my student was able to continue forward with the next two labs, including all exercises. Through exercises like creating a blog post, editing a page, and adding attachments, he was starting to understand how Confluence could help him with his daily tasks.

What did we do well?

  • Found an accessibility app and installed it
  • Walked the student through how to use it
  • Provided 1:1 instruction during labs to ensure understanding

What could we have done better? 

  • Communicated about the student before class
  • Researched screen readers to understand the best one
  • Asked the students for a solution

Going forward, I want to identify students with accessibility needs beforehand, so that I can prepare accommodations as needed. While I have thought about this as an instructor before, now that I've had the experience and have learned from it, I am better prepared to provide a better learning experience for all of my students moving forward.

We can all do great things if we communicate ahead of time. If you or your organization have accessibility needs, let us know! We can bring solutions and custom solutions as needed. 

Topics: blog confluence culture government corporate-responsibility accessibility atlassian-products social-responsibility
5 min read

Agile Home Improvement Using Atlassian Tools

By Amanda Babb on Aug 13, 2019 11:59:00 AM

This year, my husband and I decided to FINALLY spend some money on the house. We started our conversation about home improvement at the end of 2018, thinking about “the list”: need, want, nice to have. We went through the exercise of writing separate lists to compare and prioritize. Quite frankly, I was surprised at how similar they were. We quickly realized there was a need to actually organize and prioritize instead of working on notebook paper, fridge magnets, and the occasional sticky note.

Trello vs Jira Software Cloud

When we were planning our wedding in 2015, we used Jira Software Cloud. We had a Kanban Board with tasks and actions. My husband, while enjoying the fact we had a list we could access from anywhere, struggled to actually transition the cards through the workflow. With my travel schedule what it was before we got married, I was constantly calling and texting because there were no updates on the Board. He especially hated the WIP limit I added to the In Progress column. He called it the "stop nagging me" column. In the end, it wasn't too terrible. It gave us a chance to talk about each others' annoying habits: my constant need for status updates and his inability to ever finish anything (wink). While it made our marriage stronger, it also taught both of us we needed something a little more lightweight to manage our home. 

This time, we’re using Trello. We have fewer cards and use checklists to manage the work. We still have a backlog, but it's concise and doesn't scare my husband with all the agile terminology. 

Screen Shot 2019-04-05 at 2.22.48 PM

Screen Shot 2019-04-05 at 2.20.44 PM

New Back Door with Dog Door? Check. New Ceiling Fan. Check. New Floors? Hmm...we have to research those. Floors can get pricey pretty quickly. While our budget wasn't tiny and we decided to install them ourselves, there are always hidden costs. We added a research column with a few requirements: budget, material choice, finish, and installation method (floating or glue-down). We finalized the budget and away we went. We chose a dark finish engineered bamboo (heh. get it?) and determined we could afford to do the whole house minus the wet areas (Kitchen, Master Bath, and Spare Bathroom). Several monies, a week for delivery, and a week to let the floors acclimate, we were ready to build. 

Bamboo* as the Foundation

*Not the treelike grasses of the family Poaceae. But working with Atlassian Bamboo during my day job got me thinking about continuous integration and continuous delivery while we laid down our floors. My husband and I created the project and plan. Our project name: Floors. Our Plan: LDHB (Living Room, Den, Hallway, Bedrooms). Our repository was the 90 boxes of floors stacked pallet-style. Our repository was centralized so we can both pull from the materials as needed. Our trigger for our build: moisture barrier and underlayment installed. 

The real fun was determining the Tasks. This was my first floor. While I understood the fundamentals, I needed some guidance to make sure I laid them down correctly. While he tackled the large areas, I was solely responsible for the Master Bedroom. My husband, who has laid over a dozen floors over the last few years, gave me the tasks:

  • Start in the corner of the longest wall
  • Insert spacer at the end of the board next to the wall
  • Insert two spacers for each board down the wall
  • Stop both tasks once close to the end of the wall

Pretty simple. However, my first floor required feedback. To be honest, I failed my first build based on feedback from my husband. I kept running the tasks without stopping for cuts at the end of each row. I had to remove some of my work, adjust, and rework the tasks: 

  • Start in the corner of the longest wall
  • Insert spacer at the end of the board next to the wall
  • Insert two spacers for each board down the wall
  • Stop both tasks once close to the end of the wall
  • Measure for cut piece
  • Cut piece
  • Install cut piece
  • Grab additional boards

IMG_3837     IMG_3835

IMG_3836

While it took me a little longer to get it right, the results are pretty spectacular. I was surprised at how easy it was to get into a rhythm. Once I had the right tasks, I could repeat the build relatively quickly and solicit feedback less often as I made fewer mistakes. 

Home Improvement Retrospective

Once we finished the floors, it was time for a retrospective. After all, we both learned new skills whether they were physical skills or communication skills. And you can't have Home Improvement without the Improvement. 

What did we do well?

  • Coordinated the Jobs and Tasks to make sure work was divided
  • Clear responsibilities as to who can and should do what
  • More experienced teammates provided good feedback for less experienced teammates

What could we have done better?

  • More cleaning ahead of the start date (SO MUCH DOG HAIR)
  • Earlier feedback based on the Tasks to prevent the first failed build
  • Planning for food (although our local restaurants and DoorDash drivers made a mint from us)

What actions can we take going forward?

  • Ask for feedback earlier in the entire process
  • Explain "why" each other prefers a specific technique or method
  • Freezer meals or Crockpot meals set up during the day

Continuous Improvement 

We're both feeling pretty confident now that we've tackled a relatively large home improvement project together. Trello's lightweight, flexible interface helps us better communicate and prioritize the needs versus wants of home improvement. Either one of us can add items to the backlog and we have: new interior hardware, update window treatments, etc. This way, each month we can evaluate our budget and either take on smaller improvements or hold off and make a larger improvement after a couple of months. 

Do you use any of your 'work' tools to manage your 'home' life? Contact us to share your use cases!

Topics: blog scaled-agile bamboo devops kanban culture jira-software trello atlassian-products agile
2 min read

DevOps + Atlassian = Doing it Right

By Praecipio Consulting on Sep 17, 2018 11:00:00 AM

You've probably heard about a lot of the benefits DevOps teams enjoy - more effective investments, less stressful deployments, increased collaboration and visibility, and a healthier, happier, more empowered team.  With such encouraging results, the choice to take on a DevOps approach becomes an easy one. The trickier question, then, is what products can help your team take on that approach?

Fortunately, there are thousands of applications to help get you there.

Unfortunately, there are thousands of applications to help get you there.

We've worked with hundreds of clients across virtually every industry, and we have encountered untold numbers of applications, tools, and solutions along the way. In our experience, the Atlassian stack is a top choice.

We typically see a lot of added value with each team using an Atlassian stack:

Cost-effective

The overall solution is more cost effective. Atlassian prefers to spend money on product development, rather than supporting a gigantic sales team. This enables them to build best-in-class products while keeping the price tag favorable.

Integrations

Every application in the solution is integrated. Again unlike other companies, Atlassian produces products across the entire DevOps infinity loop, which results in a number of standalone products that integrate extremely well. It's kind of like the days before Apple became a dongle company when all of their products just worked together.

Customizable

Teams can customize the products to meet their needs. Not all teams want to work the same way. Differences as large as Scrum vs. Kanban or as small as where to record Acceptance Criteria can be easily managed.

Numerous applications

The Atlassian marketplace has over 1,700 different add-ons, meaning there are options to extend into nearly any other existing application in the DevOps space. If that somehow doesn't cut it, there's also middleware like Workato to help bring systems together.

Atlassian prefers to focus on building products that people love, and we've seen and confirmed for a dozen years that teams love using the products. And after all, isn't empowering teams what DevOps is all about? 

Topics: atlassian blog devops process-consulting tools consulting-services atlassian-products
3 min read

Expedite Approvals with Confluence

By Praecipio Consulting on Aug 4, 2016 11:00:00 AM

According to IDC's 2015 report, The Document Disconnect, 76% of executives and managers in sales, HR, procurement, legal, and other departments estimate that fixing the “document disconnect” can lead to document process issues impact revenue recognition or create auditor issues. As process improvement experts, we at Praecipio Consulting love saving our clients money by mitigating wasted time and helping them do work faster. With that in mind, we've compiled our top 4 tips to get faster approvals leveraging DocuSign for Confluence to integrate your mission critical document tools. 

1. Maximize Your Macros 

Confluence macros add significant value to your document drafting process with their features and functionality. Just select from your macro options and voìla - your desired information appears! By utilizing the out-of-the-box DocuSign for Confluence macros, you can simply drop the macro for your DocuSign tabs (ex. signature, initials, date, title, and more!) into your document right inside of Confluence. Adding this functionality to your document drafting allows you to save time otherwise spent selecting and adding these approval actions outside of Confluence, and also ensures that your document collaborators can see the macros you're adding and where.

Select from the menu of macros to inform your signee of what do provide.

2. Template-ize It! 

Think of the documents you create the most frequently. From sales and marketing to HR and legal, every department has documents that need signatures and approvals on a daily basis (often multiple times a day). Save your team countless hours by creating Confluence templates for these frequently used documents and reduce unnecessarily wasted time. Your Space administrator can add these templates (including the aforementioned DocuSign macros) to your instance, in the spaces you need them, so you can now spin up your next contract with the click of a mouse. 


In Confluence, click 'Create' and get prompted with both custom and out-of-the-box templates.

3. Streamline Sending 

It's simple logic: the faster you send your document, the faster you can get approvals. However, cumbersome sending processes can keep you from firing off that contract as quickly as you'd like. Leverage DocuSign for Confluence to send documents from Confluence (including all the attachments and pages your heart desires) to not one, not two, but as many recipients as you want! Set action type and order in this same step to determine who needs to sign, who needs to receive a copy, and the sequence in which these actions will occur. 

When adding recipients inside your organization, names are pulled from your Confluence user directory so you can send even faster.

4. Track in Real-Time  

Being able to see where your document is in the approval process is invaluable when you're waiting for that proverbial ink to dry. DocuSign for Confluence provides real-time status notifications so you can track your documents, from sending to completion. By simply clicking the DocuSign lozenge at the top of your Confluence page, you see what stage your document is in and who has completed what action. Additionally, clicking the status to see approval actions on the document in DocuSign. This level of visibility allows you to see when you're DocuSign envelope has been created, sent, and signed to give you the most accurate document tracking. 

View the status of all your DocuSign Envelopes in one streamlined view.

Improving processes relies heavily on cutting our unnecessary intermediary steps that can become blockers. It's these steps that, unchecked, can cost a company thousands of hours that could otherwise be spent focused on core competencies. As process experts, we recommend to all our clients- from 20 person startups to Fortune 5 enterprises- to ask themselves the following questions regarding their processes:

  • Can it be repeated? 

  • Can we automate it?

  • Can we eliminate unnecessary steps?

By optimizing your repeatable e-signature processes with DocuSign for Confluence, your organization not only saves time, but also reduces document processing issues that cut into profit or jeopardize compliance with auditing agencies. 

Ready to expedite your e-signatures? Get DocuSign for Confluence and start getting your fastest approvals.

Topics: atlassian blog confluence experts hipaa marketplace process-consulting regulation sign service-level-agreement tracking compliance docusign e-signature fda integration productivity atlassian-products marketplace-apps bespoke
1 min read

Stash in the Enterprise: Meet Stash Data Center

By Christopher Pepe on Sep 17, 2014 11:00:00 AM

Atlassian shot into the Enterprise with the release of their revolutionary JIRA Data Center in July, followed by Confluence Data Center in August. Major companies worldwide relying on Enterprise-level, mission-critical processes rejoiced- and now, they have even more reason to celebrate! Now Stash, the popular source code management for Git, is the newest Data Center offering from Atlassian. Currently in its beta version, the first and only platform of its kind to provide a highly available, scalable solution to collaborative Git teams of unlimited sizes with countless products and processes, Stash Data Center brings optimal uptime, the utmost reliability and unlimited scalability. It's only been a week since Scott Farquhar and Mike Cannon-Brookes introduced us to Stash Data Center in the Opening Keynote of Summit, but the IT community is already buzzing over the newest addition to the Atlassian Enterprise family!

Let's meet Stash Data Center!

AVAILABILITY

Using active-active node clustering, your Stash instance is always up and running! Should a node go down, the load balancer distributes the processes of the failed component to keep your workflow moving and kick off node repair. Once the node is fixed, Stash Data Center automatically updates your data with rapid re-indexing so you never miss a beat.

SCALABILITY

Whatever size your instance, Stash Data Center scales to your needs. The platform ensures your Git repository can be accessed quickly, efficiently and at all times- no matter how many users and functions are running concurrently. Have more data than you can handle? Just add another node to your instance to help share the load

SECURITY

Control who has access and permissions within your Git repository with Stash Data Center's robust security options, as well as customizable workflows to get the right code to the right people. Operating on premise and behind the firewall and using global, project, repository and branch level permissions, Stash Data Center provides the safest way yet to run mission-critical Git processes.

Atlassian thrilled new and existing users across the world with their six big product announcements and Enterprise teams everywhere cheered over Stash Data Center! 

Topics: atlassian blog atlassian-summit best-practices bitbucket enterprise reliability repositories scalability uptime data-center git high-availability atlassian-products
4 min read

Jira 5's Social Perks

By Praecipio Consulting on Mar 2, 2012 11:00:00 AM

Jira 5 is a brilliant platform for collaboration, connecting the people, activity and applications you work with every day.

Software development involves your entire organization, and good software becomes great when you bring everyone into your development process. Atlassian Jira 5′s here, connecting the dots between the development process and the rest of your business.

Your Platform for Collaboration

Software’s the center of much of our world today: it’s in your car, on the phone in your pocket, and it shapes how you work with teams, projects, and organizations.

Jira sits at the center of your software development, from initial feature planning and assigning work, to tracking development work and testing, to managing project status and the final release. Jira 5 takes collaboration to new levels by connecting people, activity, and applications around software development.

People & Teams

Jira 5 has two powerful new ways to bring people into the conversation: ‘@mentions’ and sharing.

While Jira’s email notifications are great for keeping everyone up-to-date with the issues they’re working on, sometimes you need to bring others into the conversation who might not be actively participating in an issue already.

With Jira 5, simply @mention any user in a comment or description and they’ll receive an email indicating they have been mentioned. Autocomplete lets you select usernames on the fly and Jira makes it easy to track who is involved in the comment stream.

The Share button lets you quickly send out a broadcast-style ‘FYI’ to people and teams you are working with.

Similar to sharing in Confluence 4, you can now share issues and saved searches by simply adding a user’s name or email address and typing a quick note with some details.

Activity & Applications

With new improvements to activity streams and issue linking, Jira 5 is the central place to stay up-to-date with what’s happening on your projects.

Remote issue links allow you to connect Jira issues to any website URL or application. This is great for connecting Jira issues to pages in Confluence or issues in other instances of Jira. External applications can also link to Jira issues directly to any Jira issue using the new Jira REST API.

Activity streams now show remote activity as well. In addition to real-time updates from Jira, all other Atlassian products connected via Application Links will automatically show up in your feeds. This includes changes to Confluence pages, Bamboo build status, and source activity from FishEye, and more.

Remote applications and plugins can also add events their own to Jira activity streams.

Connecting the Dots

Atlassian tools aren’t the only applications you use alongside Jira… so Atlassian’s excited to share some killer integrations to connect the tools and teams you work with every day. Here are a few examples of how development teams are connecting with the teams around them.

Development to QA

QA teams spend their time writing tests, planning execution cycles, running manual tests, kicking off automation scripts, and providing status updates in a test management tool like Zephyr. Developers spend time in Jira, managing and tracking their own daily work, or planning work with their team.

Jira 5 Activity Streams bridge the gap between tools like these, providing real-time updates between Zephyr and Jira whenever major activity happens, such as:

  • beginning testing on a particular project or version/sprint/iteration
  • a particular test execution cycle starting
  • a brand new bug being filed or modified

Developers and anyone working in Jira get a running feed on testing activities in Zephyr, as they occur, without having to reach out to those team members to chase up status updates.

Development to Product Management

Confluence is a great tool for product managers to work on unstructured content, like requirements or specification docs. These are often directly related to one or more issues in Jira.

With Jira 5, it is easy to create a two-way link between Jira issues and Confluence pages. Simply paste the URL to an issue into any Confluence page and the Jira issue will automatically be updated with a link that page.

Development to Customer Support

It doesn’t stop with Confluence. Remote issue links in Jira 5 connects Jira issues to other items the teams you work with use:

  • a document in Box
  • a customer record from Salesforce
  • a support ticket in Zendesk
  • a discussion topic from Get Satisfaction
  • and more..

Your Platform for Integration

Jira 5 makes it easier for everyone to consume and develop plugins with two huge announcements around APIs: a stable Java API and a brand new REST API.

The stable Java API means every Jira customer can rest assured that all Jira 5.0 compatible plugins will be forwards compatible with Jira 5.x releases. Atlassian wants the best possible experience for all Jira users, so Atlassian is committed to investing in this set of stable APIs to support developers integrating with our tools. You won’t need to wait on a plugin when the next Jira 5.x release comes out – you can upgrade right away, knowing all plugins built using this new stable API will be forwards compatible!

The Jira 5 REST API gives you a new way to work with issues remotely – including the ability to search, create and link issues, and add remote events into the Jira activity stream.

Get Connected with Jira 5

Jira 5 integrates with the tools developers and other teams use to help software development stay connected to the rest of the organization. Sharing and mentions make it easy to bring others into the conversation. Remote issue links keep dynamic, relevant information in a central place. Activity streams keep you updated on what’s happening in and outside of Jira in real-time.

Jira 5 is the center of software development, connecting people, activity and applications you work with every day, helping you make great software.

Topics: jira atlassian blog facebook management software sprint stream twitter zephyr collaboration development organization atlassian-products

Continuous Integration Domination: Jira Issues + Bamboo Builds

By Praecipio Consulting on Feb 8, 2012 11:00:00 AM

 

 Here’s a video overview of Atlassian Bamboo’s integrations with Jira. Learn how these two powerful tools combine forces to improve efficiency, traceability, and coordination across your product team. Read more on Jira here, and discover more ways to achieve continuous integration Zen with Bamboo over here!

Topics: jira atlassian bamboo issues videos tools continuous-improvement integration atlassian-products
2 min read

Team Calendars 1.6 Released - Share Your Custom Dates

By Praecipio Consulting on Nov 28, 2011 11:00:00 AM

Atlassian’s Team Calendars development team has been working hard to make Team Calendars the glue between Jira and Confluence. They’re excited to announce that their next major release - Team Calendars 1.6 - is available for download now!

Since Team Calendars 1.0, you’ve been able to map default date fields in Jira – issue and version due dates – on a Jira Calendar for everyone to see in Confluence. This was really helpful for Product and Project Managers to visualize the schedule of a project. However, folks have since told Atlassian that these are not the only dates important to teams. Atlassian listened, and with the release of Team Calendars 1.6, they’ve extended the Jira Calendar type to support your custom date fields in Jira.

Display Custom Date Fields from Jira on Calendars in Confluence

If you have custom date fields for your Jira Projects – ‘QA Due Date’, ‘Scheduled Deployment Date’, etc – you can now map them on a Jira Calendar inside of Confluence.  It’s quick and easy to set up from wither the the ‘Create Jira Calendar’ and ‘Edit Jira Calendar’ dialogs.

The custom dates fields you select for any given particular Jira Project will show in month, week, and list views. When you combine your Jira and People Calendars you’ve got a solution that gives your team a better understanding of a project’s progress and the ability to identify potential resourcing issues that may impact its delivery.

How can this feature help you?

If your team is using Jira for project tracking or change management, check out this post to learn how Team Calendars 1.6 can help your team deliver projects on time, all the time, and keep track of when changes were made to your internal systems.

Losing track of all these new features?

We don’t blame you! Here’s a quick review of what Atlassian’s been up to, in case you missed it.:

Enjoy and keep your eyes open for a little present from Atlassian’s Team Calendars Development Team just before Christmas.

Topics: jira atlassian blog calendars confluence project release software development atlassian-products bespoke

Praecipio Consulting is an Atlassian Platinum Partner

This means that we have the most experience working with Atlassian tools and have insight into new products, features, and beta testing. Through our profound knowledge of Atlassian environments and their intricacies, we can guide your organization as you navigate these important changes.

atlassian-platinum-solution-partner-enterprise

In need of professional assistance?

WE'VE GOT YOUR BACK

Contact Us