Blog

+1 512 266 8271 

Wednesday, May 23

6 - 9 p.m. PT

W Hotel San Francisco / SPiN

 

Join Praecipio Consulting, xMatters, and MoogSoft for a fun and interactive Incident Management Game Day at the W Hotel San Francisco (Laptops required!).

How fast can you resolve an incident? Find out how Atlassian and other ITSM tools can help reduce MTTR and provide world-class IT support.

From application monitoring to alerts, to issue tracking and team collaboration, the most effective IT teams leverage automation and integration for record-breaking mean time to resolution of incidents. In this special, hands-on workshop, attendees will interact as teams in a simulated service desk environment and respond to incident scenarios with a streamlined ITSM toolchain including Atlassian's Jira Service Desk, HipChat, StatusPage and others.

Through friendly competition and collaborative retrospectives, attendees will learn how to push alerts to the right resources, through the right platforms, for highly responsive swarming and troubleshooting.

Who should attend?
If you're an IT pro this one is definitely for you! But there's something for non-IT folks, too. Designers, technical writers, project managers - everyone - can learn how to participate in providing a better customer experience through a service desk simulation.

What else should you know?
Admission to this event is free and includes a delicious dinner menu, drinks, ping pong to follow at SPiN. We'll also be offering cool swag and sweet door prizes. Bring a laptop, and YES, bring co-workers that would be interested in this workshop.

When:

Wednesday, May 23
6-9 p.m. PT

Where:

Workshop:

W Hotel San Francisco

181 3rd Street

San Francisco, CA 94103

Drinks and ping pong:

SPiN

690 Folsom St #100

San Francisco, CA 94107


 

 

Praecipio Consulting was recently named one of the first New Relic Navigators in New Relic's Partners Program. As an Atlassian Enterprise Platinum Solutions Partner, Praecipio Consulting has also developed strong partnerships and expertise with a variety of complementary technologies, like New Relic, to ensure its customers are implementing the most effective solutions.

The New Relic Navigators Program was designed to help organizations interested in using New Relic to drive speed and visibility for joint customers with cloud migration best practices.

The program required Praecipio Consulting sales, delivery, and support team members to become trained and certified as New Relic Certified Performance Pros, learning all there is to know regarding the New Relic platform and how to build its capabilities around services for cloud migration and application performance monitoring.

Praecipio Consulting, founded in 2006, is a business process management and technology consulting firm leveraging the Atlassian toolset to deliver first-class solutions for DevOps, Agile, and IT Ops practices. Praecipio Consulting services include process and technology consulting, managed services/hosting, and product and software development. As an Atlassian Platinum Solutions Partner and process expert, Praecipio Consulting leverages the best technologies and methodologies to enable true DevOps transformations.

Introduction 

Custom macros are a popular, supported, and versatile addition to any confluence page. Confluence users are able to use macros by making their own, searching the macro library, or by getting access to additional macros through add-ons. If you are making your own macro through an add-on, you will know that the parameter types, aka fields, are limited to the following: 

    • boolean - displays a check box.
    • enum - displays a select field.
    • string - displays an input field (this is the default if unknown type).
    • spacekey - displays an autocomplete field for search on space names.
    • attachment - displays an autocomplete field for search on attachment filenames.
    • username - displays an autocomplete field for search on username and full name.
    • confluence-content - displays an autocomplete field for search on page and blog titles.

Using JavaScript and Soy templates, you are able to inject custom parameters into a macro. The following tutorial is an example of a custom field injected into a basic macro form. The goal is to create a multi-select drop down menu comprised of static predetermined menu items. Note- JS functionality to create a multi-select list and the CSS are not included. 

 

Steps for injecting an element into a macro 

Building the macro

Example code of plugin.xml 

<xhtml-macro name="macro-list" key="macro-list" class="your.class.name"  documentation-url="#"
             icon="/path/to/yourPic.jpg">
    <category name="external-content"/>
    <parameters>
        <parameter name="User" type="username"/>
        <parameter name="Page" type="confluence-content"/>
        <parameter name="StatusSelect" type="string"/>
        <parameter name="Status" type="string"/>
        <parameter name="Width" type="percentage" default="100%"/>
        <parameter name="Max Results" type="int" default="30"/>
    </parameters>
</xhtml-macro>

 

Macro prior to injecting content

 

*Note: The "Status" parameter is not visible in this image. That is because the element is hidden with CSS. More on why the element is hidden in the JavaScript section

 

Configuring the Soy template multi-select code

{template .multiSelect}
    <div class="status-container">
        <div class="closed-status-margin status-selected-container macro-input-fields text">
            <span class="aui-icon aui-icon-small aui-iconfont-arrow-down select-icon" onclick="toggleStatuses()"></span>
        </div>
        <ul class="status-list hide-statuses">
            <li value="created" onclick="statusSelect(this)">Created</li>
            <li value="deleted" onclick="statusSelect(this)">Deleted</li>
            <li value="sent" onclick="statusSelect(this)">Sent</li>
            <li value="correct" onclick="statusSelect(this)">Correct</li>
        </ul>
    </div>
{/template}


JavaScript injection

JS code with explanation

//Run function on ajaxComplete to capture edit macro view. 
$(document).ajaxComplete(function() {
	//looking for the macro-list macro to start running
	if( AJS.$("table[data-macro-name = 'macro-list']")){
    		//must verify that the MacroBrowser is available to prevent errors
			if (AJS.MacroBrowser) {
			//override command that selectes the ds macro and the field/s selected
    		AJS.MacroBrowser.setMacroJsOverride("macro-list", {
        		fields: {
            		//calls anonymous function on string fields
            		"string": function (param) {
                		//checks specifically for the string input we want to inject to
                		if (param.name == "StatusSelect") {
                    		//calls our function with the input's selected string param
                    		return handleSpacesLookup(param);
                		}
            		}
        		}
    		});
		}
	}
});
//globally available but only called if the above criteria is met
function handleSpacesLookup() {
    //grabbing the div that surrounds our selected input/param
    var paramDiv = AJS.$(Confluence.Templates.MacroBrowser.macroParameterSelect());
    
	//create a variable for our desired template
    var docStatus = path.to.your.template.multiSelect();
    
    //setting a variable to the paramDiv that corresponds to our desired input area via ID 
    var select = AJS.$("#macro-param-div-StatusSelect", paramDiv);
    
	//adding our docStatus element to the selected div
	paramDiv.append(docStatus);

	//return the selected/created element to the macro
    return AJS.MacroBrowser.Field(paramDiv, select);
};
 
//Functional logic for the multiselect not included.  

 

Completed front-end example with JavaScript

 

 

Why is the Status Parameter Gone? 

The drop down multi-select captures the user's selection on the front end. When passing the macro form information back to the server via the preview or the save button, the Status Select format is not readable. To make sure that your information is able to be parsed, you may insert relevant information into another macro field. In this case, the user's responses are sent to the hidden Status parameter each time he/she makes a change to the StatusSelect. On save or on preview, only the hidden information is sent to be parsed. 


Potential Issues 

  • I only see an empty field when opening the edit macro, I can only see my field when reloading the page with the editable macro, OR I am getting null variable errors. 

    This may be a JS async error, which could explain some inconsistencies. Make sure that this JS file is accessible to the page, that functions are properly nested, and that the initial if clause is triggered as expected. The edit screen and dialog boxes are not connected to a page reload so queries done "on load" of the page will not be caught at this point. Use .ajaxComplete or an event trigger to re-run necessary functions. 

  • My new element works but now I am missing functionality from other parts of my page.

    Make sure that your selectors are unique and as specific as possible. Try to limit using css and JS selectors by the AUI class names as these are repeated through out Confluence. 

  • I am appending my element but only see a blank input box. 

    Your parameter type may limit the content that can be appended to it. For example, select lists cannot have non-option items added to it and will instead render a broken input box. Confirm that your template has the appropriate wrappers if any. You may need to append your template to the container instead of the parameter. 

 



By Christopher Pepe, Dragon of the West

Machine learning, artificial intelligence (AI), and other advanced technical concepts are not new to Praecipio Consulting's engineers. In their spare time, they like to experiment, solve problems, and test ideas in a variety of areas. And the way they see it is they succeed, or they learn. Praecipio Labs, formalized in 2017, has really been around since the beginning. Whether it was a problem that needed solving, or it was just innate curiosity, Praecipio Labs was there to dig in and find a solution - or just have some fun! Most of the team's activity includes a variety of topics that may not be beneficial today, but are interesting nonetheless - like AI, improving advanced systems configurations, and much more.

So, who's the fearless leader?

Christopher Pepe, the Dragon of the West, oversees Praecipio Consulting's more technical endeavors. Having studied neural networks in college for robotic control systems, he has recently revisited the topic to enjoy some of the advancements that have been made. As artificial intelligence is held up as the greatest thing the universe has ever known it seemed like the right time to jump back in. Together with a ragtag team of interested engineers, Christopher is leading the Praecipio Consulting machine learning think tank to see if they can converge on a future that is better than a bag-o-if statements.

Some of Pepe and team's early projects included the Jira Toaster and Beer Me Jira. That was just the beginning. Today, Praecipio Labs is beginning to experiment with applications for machine learning. 

Pepe's recent experiment with text generation with neural networks is one of the many learning opportunities. We explored with Pepe his most recent experiment. 

 
 

Concept

Using neural networks to generate text is certainly not novel but is a fun exercise. It is also a fairly simple problem since there isn't much preprocessing to create training data. (In most data science and AI exercises one spends the majority of the time formatting and processing data.) The idea here is simple, we want to train a neural network on a given body of text (corpus) so that it can generate similar text. In this way one can generate text in the voice of the author.

I took on this experiment to build an AI that could speak in my voice. As with any worthwhile endeavor, I learned more than I accomplished.

Approach

People approach this problem with either character based or word based inputs. Character based means that if your input is "Hi there Bob" then the network is fed "H", "i", " ", "t", "h", "e", "r", "e" and so on. If word based then the network is fed "Hi", "there", "Bob." Character based approaches allow the network to do cool things like create new words. Word-based is an easier approach and in our approach was the more successful choice with less training. Our approach used a wide-ish, shallow network instead of a deep network. That means our model memorized the corpus rather than learning the meaning of it.

Training data

In all training problems, you need a large set of training data that has inputs and corresponding outputs. For instance to build a tweet sentiment model one needs 1+ million tweets with an associated sentiment label (0=mad, 1=annoyed, 2=flat, 3=happy, 4=overjoyed) and the quality of that training data determines how good your model is. That's a big task to build on a novel data set.

On the other hand training, a text generator is a simple process. The input is some number of words and the output is the next word in the corpus. Using this paragraph as an example one input might be "On the other hand training a text generator is a" and the associated output value would be "simple." The next input would be "the other hand training a text generator is a simple" and the output would be "process." 

Stepping in this way over the corpus a number of times the network eventually converges to an acceptable point.

Goals

GPU Training

To get anywhere with deep learning one really needs to train on GPUs. There are some nuances to using GPUs on AWS, and to writing code that will take advantage of multiple GPUs. This project allowed us to figure out a successful approach to using AWS for training our models.

Intro to Recurrent Neural Networks

My intro to neural networks was in college using plain old fully connected, feed forward networks for non-linear control systems  (it was a bit more state of the art back then but would still be a fun project). Life and career keep me focused elsewhere and I've only recently jumped back in. There are a dizzying array of new architectures, and approaches to interesting problems to solve. I have long been interested in time series problems and have been focused on recurrent neural networks. This was a simple but non-trivial challenge to write from scratch.

Results

After 84 epochs the loss function was minimized to 0.1195. Providing a random sample of text from the corpus as a seed the network produced this output:

 to merge completed stories and bugfixes as quickly as possible into develop so that integration and quality testing can begin sooner. merging a feature branch into the develop branch should start a build and potentially deployment to an integration testing environment. deployments can be manually triggered, but the if automatic then one is always testing the tip of the develop branch. integration and qa testing should always be occurring on the develop branch. feature branches are where developers write their code. this keeps their work isolated from other developers until it is stable. stories are sized so that a feature branch lives for 1 to 3 days. many feature branches make up a deliverable epic. features are integrated into develop by way of pull requests. pull requests are gated merges. before the feature branch can be merged into develop the code must go through a review. this can be forced with permissions or by a convention that the team uses. the merged pull request also provides a single commit to use for cherry picking features. cherry picking process again note that this process circumvents best practices

The source corpus content is listed here. You can see that the network simply memorized and regurgitated the source.

The Develop branch is the shared branch that developers use for integration testing and to accumulate features from the product backlog. The aim is to merge completed stories and bugfixes as quickly as possible into develop so that integration and quality testing can begin sooner. Merging a feature branch into the develop branch should start a build and potentially deployment to an Integration Testing environment. Deployments can be manually triggered, but the if automatic then one is always testing the tip of the develop branch. Integration and QA testing should always be occurring on the develop branch.

Feature branches are where developers write their code. This keeps their work isolated from other developers until it is stable. Stories are sized so that a feature branch lives for 1 to 3 days. Many feature branches make up a Deliverable/Epic. Features are integrated into develop by way of Pull Requests.

Some generated samples varied or had incomplete sentences but overall this model did an excellent job of recreating the source document.

I, and the team, look forward to sharing more experiments and tests like this one soon.

Wednesday, April 25

6 - 9 p.m. CST

Sheraton Westport Chalet

 

Join Praecipio Consulting, xMatters, and MoogSoft for a fun and interactive Incident Management Game Day at the Sheraton Westport Chalet (Laptops required!).

How fast can you resolve an incident? Find out how Atlassian and other ITSM tools can help reduce MTTR* and provide world-class IT support.

From application monitoring to alerts, to issue tracking and team collaboration, the most effective IT teams leverage automation and integration for record-breaking mean time to resolution of incidents. In this special, hands-on workshop, attendees will interact as teams in a simulated service desk environment and respond to incident scenarios with a streamlined ITSM toolchain including Atlassian's Jira Service Desk, HipChat, StatusPageand others.

Through friendly competition and collaborative retrospectives, attendees will learn how to push alerts to the right resources, through the right platforms, for highly responsive swarming and troubleshooting.

Who should attend?
If you're an IT pro this one is definitely for you! But there's something for non-IT folks, too. Designers, technical writers, project managers - everyone - can learn how to participate in providing a better customer experience through a service desk simulation.

What else should you know?
Admission to this event is free and includes a delicious dinner menu, drinks, and games to follow at Westport Social. We'll also be offering cool swag and sweet door prizes. Bring a laptop, and YES, bring co-workers that would be interested in this workshop.

When:

Wednesday, April 25
6-9 p.m. PT

Where:

Workshop:

Sheraton Westport Chalet

191 & 900 Westport Plaza

St Louis, Missouri, 63146

Drinks and games:

Westport Social

910 W Port Plaza Dr,

St. Louis, MO 63146

 

AUSTIN, TX
March 27, 2018 - 9 a.m. to 5 p.m.

Join us for Atlassian Planning with Portfolio for Jira to learn everything you need to know for project planning

About the event:

Interested in learning the ins and outs of Portfolio for Jira? Join our course to get the full scoop on one of Atlassian's most powerful apps for Jira Software. From this course, you'll get an introduction to Portfolio for Jira, a comprehensive overview of how the product works, and we'll share some best practices. The course walks you through building a roadmap based on work in Jira Software, forecasting release dates, managing team capacity, and creating and sharing reports on these important topics with stakeholders. This course also includes several hands-on labs giving you an opportunity to build and refine a Portfolio plan using sample data. We will provide refreshments throughout the training, and lunch will be catered. 

Objectives

After attending this course, attendees should be able to:

  • Configure Jira Software to work optimally with Portfolio for Jira
  • Create a roadmap based on data in Jira Software
  • Maintain a live plan so it's always in sync with work happening in Jira Software
  • Understand and manage team capacity through Portfolio for Jira
  • Forecast when your project will ship or whether you'll be able to ship by a certain date
  • Adjust scope, team velocity, and release timeline to understand impacts to your plan
  • Clearly see how your work aligns to business strategy with "themes" and reporting in Portfolio for Jira
  • Use reports to communicate with stakeholders about project progress and scenarios under consideration
  • Use new levels of issue hierarchy to ensure epics and stories always map back to the big picture

Audience

Anyone responsible for setting up a Jira Software project which includes:

  • Program managers
  • Project managers
  • Product owners
  • Product managers
  • Development team managers using Jira Software


Where:

Praecipio Consulting 

5918 West Courtyard Drive Ste 450

 Austin, Texas 78730


Be a part of Atlassian’s biggest world tour, and visit us at the Atlassian Team Tour right here in Austin, TX. Get the latest product updates and learn how the right tools, paired with team practices, can strengthen your organization.

Hear from Atlassian and industry leaders in your city at this unique, one-day-only event. Spend a day exploring exciting announcements and new features, see live demos, and connect with teams in your community.

Anyone who's interested in getting the most out of their tools is welcome to come. 

 

Wednesday, Feb 21, 2017 11:00 AM - 12:00 PM CST

When your system goes down and a major incident occurs, your company is losing time, money and credibility. Fast response to disruptions and slowdowns is critical, but analyzing information from every operational touch point results in an overwhelming amount of information. And communications can be difficult when resolvers, business units, and management teams all have different schedules, priorities, and processes that are constantly changing. During this webinar, Praecipio Consulting and xMatters share ITSM secrets to modernizing incident management solutions that integrate data, systems, processes, people, and teams.

Wednesday, March 21,

5 - 9 p.m. CST

Hotel Chicago + SPiN


Join Praecipio Consulting, xMatters, and MoogSoft for a fun and interactive Incident Management Game Day at the Hotel Chicago (Laptops required!).

How fast can you resolve an incident? Find out how Atlassian and other ITSM tools can help reduce MTTR* and provide world-class IT support.

From application monitoring to alerts, to issue tracking and team collaboration, the most effective IT teams leverage automation and integration for record-breaking mean time to resolution of incidents. In this special, hands-on workshop, attendees will interact as teams in a simulated service desk environment and respond to incident scenarios with a streamlined ITSM toolchain including Atlassian's Jira Service Desk, HipChat, StatusPageand others.

Through friendly competition and collaborative retrospectives, attendees will learn how to push alerts to the right resources, through the right platforms, for highly responsive swarming and troubleshooting.

Who should attend?
If you're an IT pro this one is definitely for you! But there's something for non-IT folks, too. Designers, technical writers, project managers - everyone - can learn how to participate in providing a better customer experience through a service desk simulation.

What else should you know?
Admission to this event is free and includes a delicious dinner menu, drinks, ping pong to follow at SPiN, located right beneath Hotel Chicago. We'll also be offering cool swag and sweet door prizes. Bring a laptop, and YES, bring co-workers that would be interested in this workshop.

When:

Wednesday, March 21
6-9 p.m. PT

Where:

Hotel Chicago

333 N. Dearborn

Chicago, IL 60654

 


Wednesday, February 21, 6 - 9 p.m. PT

Join Praecipio Consulting for a fun and interactive Incident Management Game Day at the Santa Clara Marriott (Laptops required!).

How fast can you resolve an incident? Find out how Atlassian and other ITSM tools can help reduce MTTR* and provide world-class IT support.

From application monitoring to alerts, to issue tracking and team collaboration, the most effective IT teams leverage automation and integration for record-breaking mean time to resolution of incidents. In this special, hands-on workshop, attendees will interact as teams in a simulated service desk environment and respond to incident scenarios with a streamlined ITSM toolchain including Atlassian's Jira Service Desk, HipChat, StatusPageand others.

Through friendly competition and collaborative retrospectives, attendees will learn how to push alerts to the right resources, through the right platforms, for highly responsive swarming and troubleshooting.

Who should attend?
If you're an IT pro this one is definitely for you! But there's something for non-IT folks, too. Designers, technical writers, project managers - everyone - can learn how to participate in providing a better customer experience through a service desk simulation.

What else should you know?
Admission to this event is free and includes a delicious dinner menu, drinks, fun and games. We'll also be offering cool swag and sweet door prizes. Bring a laptop, and YES, bring co-workers that would be interested in this workshop.

When:

Wednesday, February 21
6-9 p.m. PT

Where:

Santa Clara Marriott

2700 Mission College Boulevard

Santa Clara, CA 95054

 


 

Available on demand: Wednesday, Dec 20, 2017 11:00 AM - 12:00 PM CST
Jira Service Desk is a powerful tool, giving teams the ability to provide great customer service, automate repetitive tasks, improve ITIL processes, and more. While Jira Service Desk is powerful out-of-the-box, there are many features you can start using in the new year to trim ticket calories, save time for new hobbies, and spend time with those you care about. In this webinar, we're going to talk about the benefits of integrating Confluence to reduce ticket amounts, how to create enhanced workflow automations that will help you save time and resources, and features that improve organizational communications. Principal Consultant Brian Nye will share expert tips on using Confluence to provide self-service options for customers, creating time-saving automations, and using "organizations" to send real-time updates to your team. 



In our last blog post, we shared with you how Portfolio for Jira can be used to plan and visualize work for any department or line of business. Now that everyone has a seat at the table, let's make sure the meal is excellent by following a trusted recipe for Jira Portfolio best practices.  

There are only two simple ingredients for a successful Portfolio implementation: Jira configuration and data integrity. 

Jira Configuration

It's important to make sure your Jira entities  workflows, projects, boards and filters  are configured correctly. While this may seem like common knowledge, some organizations overlook even the simplest mistakes when configuring their Jira instance - it's important to make sure you cover all the basics early on.

 In addition, Portfolio entities must also be determined, such as hierarchy and parent links, dependencies, and permissions. Portfolio is customizable to fit your organization's needs, and like the importance of making sure your Jira instance is configured correctly, the same goes for Portfolio - its imperative that the time is taken to set up your instance that best serves your organizations needs. 

To start, you should determine a level of organization that is larger than an Epic. If an Epic is 3-5 Sprints, this larger concept should represent a longer timeline: perhaps 6 months. You can call it anything you want, but we commonly use 'Initiative,' which is Portfolio for Jira's native language. With the Epic Parent created, Portfolio's configuration needs to know you're adding a level, and then have it mapped appropriately to the issue type. The next issue type to be created is called a 'Story,' which will include all other standard issue types, and will live between an epic and a sub-task. You can use whatever taxonomy works best for your organization; however, we have one recommendation - keep it simple!

Adding the 'initiative' level allows your team to not only get a birds-eye view of your entire plan, but also how it aligns with overall business goals

Also part of your configuration recipe is the creation of a scrum board. Boards in Jira Software are driven by filters, and you should group them into a project or project category.  A word to the wise: Don't append your query with clauses that would remove workflow statuses or remove a specific tag of work. Let the board drive what your plan would display. Keep in mind if it's on your board, it's going to be in your plan.

Now that your Jira configuration is cooking with gas, let's dig into data integrity.

Data Integrity

Portfolio brings projects and plans to life; however, its powered by the data inputted into Jira. You've heard the saying 'garbage in, garbage out', right?' Avoid bad data at all costs and follow these simple steps to keep you Jira data clean.

You can start with keeping your backlog groomed by simply resolving and closing your issues. Closed issues will disappear from your backlog and will no longer show on your board, which means the Portfolio won't display them in the plan, either. Not only is this good practice in general for Jira Software, but it will keep your Portfolio plan accurate. If you have a task or issue that has been sitting in your backlog for a year or two, it's time to clean the pantry.

Maintaining hierarchy in Jira software is critical when using Portfolio. You must close out lower-level items before closing the parent - if you complete sub-tasks and close them out, it doesn't mean you're 'in progress' in the hierarchy. No progress will be seen on the story, epic or initiative just because you close or resolve a sub-task. You should be focusing on story completion and story throughput, instead of progress at the sub-task level. Make sure you are closing and completing story level to show progress in your plan overall - again, this will maintain accuracy in planning and forecasting.

Closing your story-level tasks will show your plan's overall progress

This blog post is full, but you can come back for tasty seconds and thirds in the Portfolio for Jira: Best Practices webinar coming up on November 30 at 11 a.m. CST.

Thanksgiving is right around the corner, we can't help but think about our favorite things this time of year. We have opportunities to see family, friends and relatives, enjoy good food, and talk about everything that happened throughout the year. It is great to catch up and visit about what's happened, and what's going to happen. It's a time when families and friends reflect, collaborate, and even begin planning for the next year (because all families get along perfectly, right?).

What if you had a holiday table year-round for your organization?

If a project is delayed, or a change needs to be made, wouldn't it be nice to update the entire plan and everyone on the team at once?

Atlassian's Portfolio for Jira is the solution. 

The core of Jira Software is a workflow engine. It allows you to track issues and tasks in a predefined, customizable workflow. Now, take this awesome workflow capability, and lay a forecasting and visualization tool on top of it - that's Portfolio for Jira. Atlassian’s Portfolio for Jira is the road mapping and visibility tool used to forecast and track long-term plans, increasing visibility and business alignment. Portfolio provides a living, breathing plan for teams and leadership to stay up-to-date on existing plans, all while forecasting new long-term plans.

The best part? It's not just for software teams.

Portfolio for Jira

Portfolio for Jira organized existing marketing tasks (entered as issues) into releases and themes, giving our entire team the visibility we needed to stay on track.

Teams that can benefit from Jira Software: 

  • Human Resources
  • Operations
  • Marketing
  • Procurement
  • Legal
  • Sales
  • And more 

Because we track just about everything we do - including marketing activities - in Jira, the marketing team at Praecipio Consulting was able to use Portfolio for campaign planning and execution. As a test case, we launched a product marketing campaign for our newest add-on in the Atlassian Marketplace, Turbo Kit for Jira. Portfolio for Jira helped our team plan, forecast, manage, analyze, track and report on our campaign efforts. 

Change happens – all the time. Portfolio can help you, your team, and leadership stay well-informed on project and planning statuses, and it can also help you see the big picture and track business goals (not just your team or department!). It is the ultimate visibility tool. 

We'll dig into this a little more in our upcoming webinar Portfolio for Jira: Best Practices. Be sure to grab a seat at our table to learn more!

Learn more about Portfolio for Jira in the Atlassian marketplace.


 

Thu, Nov 30, 2017 11:00 AM - 12:00 PM CST
Portfolio for Jira serves your Agile Portfolio Management needs. It provides visibility of work breakdown and execution, estimation of project completion, and short-, mid-, and long-term scenario planning. While it is simple to use and integrate, it is highly dependent on best practices in Jira and good user discipline. Are you exercising best practices in Jira and are your users disciplined? Portfolio for Jira expert Amanda Babb will take us through some best practices, address common frustration and challenges, as well as help you plan for your best year yet! Whether you’re a current Portfolio for Jira user, or you’re evaluating it for your organization, you’ll want to attend this webinar to make the most out of your experience. 


Tuesday, December 12, 2017 6 - 9 p.m. CST

If DevOps is on your radar, and you're anywhere near Dallas on Tuesday, December 12, then join us for dinner and drinks at The Alamo Draft House - Cedars. We'll be speaking your language, discussing all things DevOps, and how we (Praecipio Consulting) and Atlassian can help dev and ops collaborate to build a faster, more reliable release pipeline.

When:

Tuesday, December 12, 2017
6-9pm CST

Where:

The Alamo Drafthouse Cinemas - Cedars
1005 S Lamar St., Dallas, TX 75215