3 min read

Can a Product Owner also be a ScrumMaster?

By Katie Thomas on Apr 12, 2021 10:21:00 AM

Blogpost-display-image_Can a Product Owner also be a Scrum Master-TL;DR: No!

Can one person hold both the Product Owner (PO) and ScrumMaster(SM) role in an Agile team? It's a question that a lot of companies starting their way through their Agile transformation will ask themselves (and us!). The Scrum team has three specific roles: Product Owner, ScrumMaster, and (most importantly) the Development team. It's clear why the question of combining SM and PO comes up so often - trying to figure out where current roles fit into the new dynamic can be a challenge for an organization, especially if your teams are now smaller and you don't have enough resources to fill the role of an SM and PO for each team. 

However, combining these roles is the biggest disservice you can do for your Agile teams. It may seem like a small tweak to the model, but given the functions of the two roles, you are setting up your teams for failure. Let's start with the definitions of these two roles so we can see why that is. 

Product Owner

The focus of the Product Owner is on the Product, as you might have guessed by now.  According to ScrumAlliance.org, "The Product Owner defines the what--as in what the product will look like and what features it should contain." The PO is responsible for maintaining the product backlog, and are responsible for communicating with stakeholders internally and externally to identify what the development team is working on. In their day-to-day, they are responsible for creating and prioritizing backlog items and communicating with the team expectations and acceptance of complete work items. 

ScrumMaster

The focus of the ScrumMaster is the team. "The ScrumMaster helps the Scrum Team perform at their highest level. They also protect the team from both internal and external distractions. ScrumMasters hold the Scrum Team accountable to their working agreements, Scrum values, and to the Scrum framework itself", as defined by ScrumAlliance.org. Where the PO is focused on What, the SM is focused on Who and How.  Arguably, the most important part of this definition is the emphasis on protecting the team. Internal distractions often come in the form of scope creep – new scope being introduced once work has already been committed to. In Scrum this often looks like new stories or bugs being introduced in the middle of a Sprint, and the job of the SM is to prevent this from happening as much as possible.

While I'm sure that we all know that some scope creep is inevitable (unless perhaps you're inhabiting the perfect utopia of business environments, in which case, I'll keep an eye out for my invite), but it can get out of hand quickly if there is no one on the team who is able to push back against the business. 

Okay, so why can't they be the same person?

By definition, the role of the ScrumMaster is to protect the team from the Product Owner (and the stakeholders that they are representing). Blurring the lines between these two roles mean that there is no one to push back when scope is added last minute, or ensure that the team is sticking to Scrum best practices, despite heavy workloads.

The most common outcomes that we see when these two roles are combined are:

  1. Tons of scope creep. Just, loads of it. All over the place.
  2. Sprint commitments are consistently not met because the team is being asked to do more work than they've agreed they are able to. 
  3. Product Owners assign out work to the team , as they are now "Managing" the team. 
  4. Buggier products –  after all, if I'm a developer trying to get through more work than I've acknowledged I can do, quality is inevitably going to suffer

Overall, not great!!

So what should I do then?

In a perfect world, you should have a single ScrumMaster per team, and Product Owner per product. This means that Product Owners can span multiple teams, if the teams are working from the same product backlog, but ScrumMasters are dedicated to a single team. If you don't have enough resources to commit to this model, in the short term, a ScrumMaster could potentially span more than one agile team - but I would say no more than 2 - after all, one person can only attend so many Scrum ceremonies while also being available to unblock their teams. 

However, the long term success of your Agile transformation means that it's time to start planning to fill those roles. Combining these roles will almost certainly decrease the effectiveness of your move to agile, as your teams are left unprotected and (likely) overworked. 

Looking for more information on Scrum best practices? Check out Sprint Planning - How long should sprints be? or Agile Batch Size: An Ode to Laundry

Topics: blog process scrum workflows project-management agile
3 min read

Should scrum teams track their time?

By Amanda Babb on Feb 5, 2021 8:03:49 AM

Blogpost-display-image_Should scrum teams track their time-"How many hours are in a Story Point? Pink. Because penguins don't like ice cream." -Amanda Babb in every conversation about hours and story points. 

While I use this example as a cheeky way to say the two methods of estimation (hours and story points) don't coincide, the reality, of course, is much more complex. Business and product teams typically think in terms of dates and schedules. Development and operations teams typically think in terms of level of effort. That's not to say story points and dates do not nor will ever coincide, it's a matter of how to speak each other's language. 

What is a Story Point?

Our Dragon of the West, Christopher Pepe, explained it well in a previous post. Humans are terrible at numbers. That's why we have so many ways to express things without using numbers. For example, I have Big Dog (Leonard) and Tiny Dog (Howard). Tiny is small in comparison to Big Dog. However, at 50 pounds, he's not small compared to, say, a Chihuahua. This is what we call relative estimation in the agile world. This thing is larger or more complex than the other thing over there: it will take a larger level of effort to complete. 

Computers, on the other hand, are wonderful at numbers. It's part of the reason we invented them. In Jira Software, a story point is simply the numerical expression of a relative estimate. When we need to understand the level of effort of more than one thing, we aggregate the relative estimate into a total level of effort. This is known as the commit in a velocity chart. As we complete work, we burn down the level of effort until we understand what's left. At the end of a sprint, we determine whether we met our commit or not. The completion of the work over several sprints determines our velocity. From there, we can reasonably predict the level of effort we can complete during a sprint. 

Why can't a team estimate in hours? 

It's not a matter of can't. At Praecipio Consulting, we've seen many teams succeed well in estimating their level of effort in hours. However, this involved a significant effort to run time studies on routine tasks for the team. In a time study, an outside party will watch a person do a task and time it. Then watch them do it again...and again...and again. Then, the outside party watches another person perform the same task several times. The outside observer will continue with this until they feel they have sufficient data to make a reasonable assumption (read: average) of the time it takes to complete said task. Rinse and repeat for all tasks all personnel complete in a day and through out the week. 

Estimating in hours works well in repetitive work environments. The same tasks must be completed the same (or similarly enough) throughout the day and week. However, when we're thinking about software development, we all know this is rarely the case. What may seem like a simple feature request can become a significant effort when looking at how the new feature interacts with the rest of the services, modules, or products. Yes, we've done something similar before and it took four hours. But what has changed since the last time we implemented something similar? What else have we deployed? Did we change our methods? Are we integrating this with another system? Have the APIs been updated or changed? How many releases have been performed since the last time we did this? 

The shoulds and shouldn'ts of tracking time in Scrum

Why are teams being asked to track time when they estimate and understand level of effort in story points? In a word, Money. Under complex financial and regulatory practices, most businesses report quarterly earnings to regulatory bodies and markets. The best way a business has to gather and report this information is through complex financial systems that aggregate data from inputs across the organization. One of the more critical inputs? Time tracking. So how should we and shouldn't we track time in a scrum team? 

  • You should establish the minimum time guideline such as 15-minute or 30-minute increments
  • You should not expect accuracy down to the minute for a given task
  • You should expect the team(s) to continue to estimate their level of effort in story points
  • You should not make the team switch to hours to estimate their level of effort
  • You should centralize where the team should track time
  • You should not expect the user to log in to multiple tools to track time
  • You should download our Lean Budgets White Paper which details different ways of managing the data and provides a solution in Jira Align
  • You should not expect to implement a fundamental change in financial tracking and reporting across your organization without help

At Praecipio Consulting, we have implemented several solutions to this problem across industries and with all sizes of organizations. For help regarding how your teams can balance time tracking, scrum, and financial reporting, feel free to reach out to us! 

Topics: blog plan process scrum lean-budgets agile
3 min read

What’s the Difference? Agile Coach vs Agile Consultant

By Praecipio Consulting on Jul 9, 2019 12:17:00 PM

Agile has become quite the buzz word within the software development community. Some of the most successful software companies are known for how Agile they are and how often they can release code in production. However, before becoming Agile in software development, these companies first embraced and implemented the Agile framework across the entire organization–not just with the technology team, but with HR, Finance, Biz Dev, Legal, etc. And this isn't something that they accomplished overnight. 

Becoming an Agile organization, which can take a minimum of six months to achieve, involves undergoing a massive organizational transformation – redesigning everything, from strategy, processes, teams, governance, and work culture. This is why many companies decide to hire experts when they are implementing this methodology. Not only is it an enormous undertaking, but being Agile is instrumental for the future success, sustainable growth, and continuous improvement of an organization in an increasingly complex marketplace. 

So, when you are ready to bring in the right help for successfully achieving and sustaining Agile within your organization, you may be wondering if you should hire an Agile Coach or Agile Consultant. Before understanding the differences between Agile Coaching vs. Agile Consulting, you should ask yourself:

  1. Is our organization already Agile or are we trying to be?

  2. How mature is our team?

  3. What are our pain points?

  4. At the end of this engagement, what does success look like?

Now, let's shed some light on the differences between an Agile Coach and an Agile Consultant:

Agile Coach - A Subject Matter Expert

An Agile Coach plays a similar role to the one a teacher plays in school. They studied Agile methodologies and have been trained on how to teach those methodologies to others. Agile Coaches help train all teams within an organization and manages the implementation process in order to carry out a solid transformation. The coach works closely with each team and walks them through the steps of fully embracing and adopting the Agile framework. Instead of actually doing the work for the team, Agile Coaches equip their students with proper training, education, guidance, and resources so that they can successfully implement and sustain the Agile methodology. Working with Agile Coaches is typically a longer engagement. 

Some of the most common reasons for hiring an Agile Coach are:

  1. Organization is new to Agile methodologies and needs guidance (i.e. companies undergoing Agile transformations)

  2. Scaling Agile, working across all teams or at the enterprise level

  3. Improving performance, visibility, and predictability (portfolio planning)

Agile Consultant - A Business Consultant 

An Agile Consultant, on the other hand, is a practitioner. As the word practitioner suggests, he or she puts the Agile framework into practice by using their extensive experience with Agile to navigate roadblocks and quickly resolve any problems that are preventing the organization from achieving their desired results. Unlike the Agile Coach who provides guidance, the Consultant actually does the necessary analysis and problem-solving to put your organization back on track for success before handing the reigns back over to your teams. Essentially, an Agile Consultant provides a more short-term solution.

The most common reasons for hiring an Agile Consultant are:

  1. Problem-solving: You realize the problem is beyond your teams' capabilities and you need a specialist.

  2. Your organization is not seeing the effective outcomes associated with the Agile methodology. 

  3. You want advice on what issues need to be resolved and how to quickly tackle them.

Difference Between Coach and Consultant

Now that you understand the key differences between an Agile Coach compared to an Agile Consultant, you are one step closer to hiring the right expert for your organization and even that much closer to accomplishing a sustainable Agile framework. Even though a Coach and a Consultant play different roles, they are both equally essential in promoting cultural change and overcoming the obstacles that come with successfully embracing, implementing, and practicing the Agile methodology. 

Is your organization undergoing an Agile Transformation? Learn how our approach empowers organizations to achieve a successful Agile transformation in a sustainable and scalable manner, which drives business performance and propels our clients to be disruptive, innovative leaders in their industries.

Topics: scaled-agile process digital-transformation
3 min read

Three Reasons Why Developers Love Docker

By Praecipio Consulting on May 6, 2016 11:00:00 AM

A smooth running production environment is a beautiful thing. But how do we get there? And how do we ensure that all of our production, staging/test, and development environments stay in sync in order to get there? Today, it seems like everyone in software development is talking about Docker and containers. In fact, according to the 2016 State of the Cloud Survey by RightScale, Docker adoption doubled from 13% to 27% in just one year. Furthermore, 35% of the organizations surveyed reported that they have plans to adopt it soon. 

Why has Docker adoption skyrocketed and how can those using Bamboo for continuous deployment reap the benefits? Check out three reasons why developers love Docker, and how it can provide value for your dev team. 

But first... 

What are Containers?

A Docker container packages software in a complete filesystem with everything it needs to run – such as code, runtime, system tools, system libraries – guaranteeing that it'll always run the same on any environment. Docker is all about creating consistency and encouraging collaboration. It revolutionizes how we share our environments the same way Git has changed code collaboration. At its core, Docker is about utilizing the least amount of operating system resources and dependencies needed to run an application. This focus on maximizing efficiency leads to a painless, more collaborative, and seamlessly integrated environment to test and deploy applications. 

Sourcewww.docker.com

1. Test without surprises

A crucial part of the development process is testing, whether on a local machine or in a virtual dev environment. With containers, every environment is exactly the same so changes and unexpected dependencies won't interfere with testing – saving developers time and energy from tweaking problematic environments and instances. 

Running containers on your local machine using Docker Quickstart Terminal lets you test in a consistent environment.  

2. Collaborate with consistency

Unexpected dependencies are already a hassle for one developer and becomes an even bigger headache when other devs enter the picture. Unknowns in an environment are amplified with each new team member – who knows what's on their machine or which version of Java they're running? With Docker, consistency facilitates collaboration. By starting with a known configuration in a common container, devs are always on the same page about which version to use; it's right there in the container.

Share your Docker Images with a registry like Docker Hub.

Source: https://hub.docker.com/_/hello-world/

3. Integrate with Atlassian 

Atlassian, the leader in enterprise software for collaboration and issue tracking, is the perfect complement to Docker. By pairing Docker's consistency with Atlassian's integration and automation, collaboration between development and IT ops becomes seamless. Using the new Docker Hub 2.0 with Atlassian's Bamboo, source code can be automatically built and deployed to an identical development, test, or even production environment. No more requesting environments from the IT ops teams; triggers will automatically fire from your approved pull request in Bitbucket to spin up a lightweight container in your QA environment almost instantly. Without the excess back and forth, you can go from source code to a running application in minutes. 

The Docker Task in Atlassian's Bamboo let's you run, build and deploy images and containers with ease.

Docker is picking up a lot of traction today and rightly so. Docker containers provide consistency in the turbulent world of software development environments. They allow dev and operations teams to get customers the applications they need now – all while providing a consistent environment that makes working together a whole lot easier. 

To learn more about how Docker and Atlassian can help your dev team work faster and smarter, contact Praecipio Consulting.

About Brendan Kelly

Brendan is a Consultant & Solutions Specialist at Praecipio Consulting where he enables the sales team through technical discovery, training and product demos. When Brendan isn't delivering best-in-class business technology solutions, he can be found in the Austin Green Belt hiking and bouldering. 

Topics: atlassian blog automation continuous-delivery bamboo docker optimization process standardize testing continuous-integration deployment development environment integration cicd
7 min read

Seen It, Solved It: Jira Service Desk for ITIL

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

Growth Through Change 

"Organizations that do not or cannot evolve will not last." In the business world, change is constant and necessary, especially when it comes to meeting the dynamic needs of customers. ITIL, or Information Technology Infrastructure Library, is a methodology that helps organizations effectively manage change while putting the customer at the center of the process. ITIL prescribes processes to ensure the customer's needs and requests are handled with ease – from acknowledgement of an issue through the application and evaluation of the solution. One of the greatest values of the ITIL methodology is that it embeds continual improvement into the process. The ITIL framework can be leveraged by anyone, including non-technical teams, to better manage change and serve customers. Atlassian's fastest growing product, Jira Service Desk, facilitates ITIL adoption in an organization by encouraging traceability, collaboration, and reporting. 

As business process experts certified in ITIL, we leverage the ITIL methodology in unison with Jira Service Desk to institute best practices for our clients. Here are 5 real-world examples of how Praecipio Consulting helped our clients implement lasting organizational change by embracing key ITIL concepts of automation, visibility, knowledge base, change management and evaluation, and continuous improvement. 

Automation

"Using service automation to streamline both simple and more complex workflows of course impacts the overall efficiency of the organization... it also allows for a much better end-user experience for everyone at the company." - ITIL beyond IT: What is Service Automation & Service Relationship Management?

Problem: A major utility company powering the U.S. Eastern seaboard was manually reporting security equipment issues and coordinating with external vendors to fix the issues. This manual process was prone to errors and didn't allow for tracking of service level agreements (SLAs), which would determine which vendors were breaching their contracts. The company was using spreadsheets to track these crucial assets and their maintenance. The spreadsheet system was inefficient and created duplicate versions – leading to confusion, frustration, and waste. Furthermore, the spreadsheets could not track SLAs for Acknowledgement or Resolution for vendors.

Solution: To reduce redundancy and enforce SLAs, our experts implemented Jira Service Desk for the major utility company. By replacing their spreadsheets with Jira Core and Jira Service Desk, we helped them add a level of automation to their workflow. This reduced waste of time and resources, allowed for better communication with third-party vendors, and created a clear path for escalation. The custom configuration we created for the company maintained their security, while also allowing vendors to be a part of of the conversation. Furthermore, reporting features from both Jira Core and Jira Service Desk allowed for a central point of truth. The utility company could check the status of service tickets and see how well vendors were adhering to their SLAs. Through the process of improving their security equipment reporting and vendor coordination, the company found other areas of improvement and have chosen to continue working with us to maximize those workflows. 

Visibility

"It can be very difficult to know the health of your service desk, run reports, and find way to improve your support if you don’t have the right data." - The ABCs of Jira Service Desk: measuring success

Problem: A major U.S. waste management company wanted to adopt a more structured reporting system, replace an old enterprise software application, and incorporate the ITIL framework into their organization. The company's goal was to standardize tools in order to improve communication and rally around a consistent project management methodology. The waste management company desired a suite of tools with the ability to integrate functions across IT service areas, leading to better service for the end customer.

Solution: In addition to implementing several other Atlassian products, our experts helped the company leverage Jira Service Desk to achieve their business goals. We helped them create a central application with the ability to distinguish request types through a structured workflow. This included a more robust user interface to better triage issues and send them to the appropriate teams. The ability to categorize requests and label them with levels of urgency allowed the company to have better reporting, leading to improved enforcements of SLAs. 

Knowledge Base

"[A knowledge base] gets [customers] the help they need at the speed they’ve become accustomed to – i.e., in the time it takes to swipe around on their phones – and it frees service desk agents from stressing out while anxious customers wait on hold or answering the same question over email for the 10th time this week." - 4 tips for getting started with knowledge management

Problem: A large, private U.S. university wanted to revamp an old software application and replace it with a more robust and dynamic knowledge base. The university's goal was to increase usability for both their students and faculty regarding technical and campus-related questions, deflecting tickets by providing requesters with FAQ's and other resources to help them self-serve to find their answers. 

Solution: Our experts helped the university leverage Jira Service Desk and Confluence to achieve their goal. Combining Jira Service Desk with Questions for Confluence (a Confluence add-on that provides a knowledge base inside the already powerful wiki tool) allowed the university to implement a centralized knowledge database. Jira Service Desk allowed for better help engagement using queues and other helpful functionalities. Questions for Confluence empowered external users to help themselves by accessing a database of pre-answered questions, without tying up service desk agents with redundant problems.

Change Management and Evaluation

"Listening to your customers is the single most important thing you can do for the health of your company." 5 tips to transform your IT team from zero to superhero

Problem: The largest provider of support services to general and multi-specialty dental groups in the United States needed the ability to receive and respond to client feedback in addition to handling client issues. They did not have a clearly defined process for patients to interact with the organization and to raise issues. Their marketing team was searching for a new software tool that would manage feedback in a way that led to issue resolution and change management. The team's ideal tool would be able to enforce and report on multiple SLAs through issues submitted via the company's public website.

Solution: Our experts helped the dental corporation adopt Jira Core and Jira Service Desk to manage issue tracking and change management. With Jira Service Desk, the company was able to cleanly sort through client feedback and create a workflow to address issues that arose. Beyond managing client feedback, the dental corporation also used these tools for clinical tasks, billing, and other activities that needed life cycle tracking. In addition to tracking, the Atlassian tools helped the organization evaluate the effectiveness of their changes and quantified the improvements made – empowering all teams, not just marketing, to better serve their customers. 

Continuous Improvement

"With a single-product approach, configuring an SLA or modifying a workflow is easy, because they share core processes." How Jira Service Desk approaches ITSM 

Problem: A major U.S. insurance company was using three different software applications for code management, issue tracking, and service desk management – leading to inefficiencies and miscommunication. Their use of three separate applications resulted in duplicate tickets and the inability to enforce SLAs across the organization.The insurance company wanted to improve these processes and embrace ITIL's practice of continuous improvement. 

Solution: Our assessment encouraged the company to adopt a single application, Jira Service Desk, to provide a single source of truth. With Jira Service Desk, there was a common point of collaboration for issue management. This reduced duplicate tickets and saved valuable time and resources. Leveraging entities, workflows, and issue linking, we helped the insurance company align their processes to make reporting and enforcing SLAs easier, more efficient, and more effective. By strengthening their ability to track what changes are needed and to act upon those needs, we helped them develop a cycle for continuous improvement.  

ITIL for One, and ITIL for All 

"Just because one service desk streamlines the IT and service departments, it doesn’t mean that other teams can’t also benefit from them." - 5 tips to transform your IT team from zero to superhero

These real-world examples from our clients highlight how ITIL and Jira Service Desk can help organizations evolve and change – without the growing pains. ITIL concepts of automation, visibility, knowledge base, change management and evaluation, and continuous improvement aren't just for IT teams. These powerful ideas also provides immense value to other parts of any organization, technical and business teams alike. At Praecipio Consulting, we excel at leveraging the ITIL methodology and Jira Service Desk to help organizations do what they do better. Want more proof? Contact us to learn how we can help your organization evolve and do your best business. 

Topics: jira atlassian blog scaled-agile automation business confluence process standardize workflows traceability collaboration continuous-improvement integration it itil itsm jira-service-desk operations reporting white-paper
5 min read

All-Star Incident Management: How to Be Like Mike

By Praecipio Consulting on Mar 21, 2016 11:00:00 AM

The best teams sync with each other. Think of the intangible magic conjured by the Championship-sweeping Chicago Bulls of the 90's, helmed by Michael Jordan. They ran their offense to perfection, playing to the strengths of each team member and executing each step in perfect rhythm to put points on the board. Any member of those teams will tell you their success came not only from having high-performing people but from working together within an established offense, or process. Because they bought in and trusted the process, each team member knew his responsibility at all times. The team ran time-tested methodologies for getting the win, adjusting as needed after analyzing the other team's strategy. Basketball is all about strategy, process, and teamwork.


Now think of that team that loses to the Bulls- that loses to everyone. The team that's always scrambling after a broken play, unsure of how to set up their offense or what to do after a missed basket. They spend the entire game – and all their focus and energy – trying to just keep up. These are the teams that don't trust in their process, usually because it hasn't worked in the past or they haven't learned how to work with each other. It's hard for each player to handle his responsibilities because he feels like he has to win the game by himself instead of together with his teammates. It's not a good way to win games, and it's certainly not a good way to structure your IT team.

As Atlassian Platinum Enterprise partners and experts in all things process, we've got your playbook for all-star incident management:

Top 3 Tips for Championship ITSM

      1. Track your failures for greater success.

Basketball teams use stats to identify strengths and root out weaknesses. Tracking areas for improvement is key. When agents solve issues in silos they can't tell when an issue reoccurs or causes other issues, indicating a root cause that should be investigated. Ability to link issues is paramount to give your problem-solvers visibility into what keeps going wrong and, ultimately, what should be changed to keep it from happening again. 

2. Success loves preparation.

The 90's Bulls probably lost count of how many times they ran the same plays during practice. The better we prepare, the more successful we are. In the IT world, reporting, documentation, analytics, and other functionalities of our ITSM tool of choice make it easier to prepare well. When we're able to forecast issues based on prior knowledge, we're prepared for what's ahead. Data like a team's sprint velocity or average resource allocation per type of project inform planning for all foreseeable project outcomes.

3. Establish repeatable processes.

Michael Jordan is one of the most successful athletes in history because he was the first one in the gym and the last one out. He was always running drills and perfecting his shot, establishing repeatable processes that became muscle memory. Applying this concept to your organization allows your team to handle day to day operations with relative ease - each agent knows what to do, and they trust in the established process. This is a key to effective incident management and it allows you to focus on improving and advancing solutions rather than fighting fires.

Seen It, Solved It: Major U.S. Insurance Provider

Ready to see these plays in action? Here's how these 3 tips helped our client do better work, faster.

THE PROBLEM

Issues are like potato chips: you never have just one. In a business, any single issue that arises is usually experienced by multiple end-users and often starts a domino effect that causes more related issues. Without the ability to see across all these related issues, each agent responding to an individual issue only sees just that, failing to see the forest for the trees and moving on with an issue fix that doesn't address the root cause.

A major U.S. insurance provider came to us with concerns about their incident management. They already knew that their processes were poorly designed and not well adhered to, but they needed help figuring out how to improve them. In particular, incidents were not well documented or properly managed, putting them at risk for violating regulatory compliances. The client's struggles included:

  • ITSM Processes with No Buy-In (Too complex, too outdated, or too redundant)
  • Lack of Integration Across Tools (Lots of time wasted in context switching, Inability to analyze across platforms)
  • No SLAs or Metrics to Gauge Effectiveness

In short: They were focusing all their time and resources trying to just keep up, but could never get ahead in the game.

THE GAME CHANGER

Enter Coach Praecipio Consulting and Jira Service Desk to deliver a slam dunk incident management solution.

 
New Process Playbook

Because our client had different tools for managing incidents, their lack of visibility across platforms led to slow speed to market with fixes. Jira Service Desk not only solves this issue, but also supports best practices for incident management. By standardizing automated workflows and establishing lean processes, our client is no longer burdened by redundancies and can gather meaningful metrics across incidents.

 
Pass to other Players, er... Tools

In order to deflect the amount of incoming tickets, Jira Service Desk integrates with Confluence to provide a self-serve knowledge base. By leveraging this integration, our client gets back time and resources, no longer tied up on tickets to which an answer already exists. Leveraging machine-learning, the Confluence knowledge base identifies frequently searched topics and strengthens its query language to provide the best answers to questions around incidents. 

 
Set the Shot Clock

As an insurance provider, our client needed to ensure that they stayed within regulatory compliance with vendors and customers alike. Configuring SLAs in Jira Service Desk allows for the client to start the timer the minute a ticket is assigned, tracking time to resolution and producing reports to identify SLAs in danger of being breached. By doing this, the client gains visibility into incident management and can use metrics against goals for continuous improvement. 

Be Like Mike

Like the Bulls' 1-2 punch of Michael Jordan and Scottie Pippen, the tandem of Jira Service Desk and experience-driven process expertise gives our clients a heightened ability to execute ITSM best practices and keep their teams in a cycle of continual improvement. Maximizing your processes makes your day-to-day work simpler, allows you to focus on higher level objectives for better business, and helps you get numbers on the board (with dollar signs in front!). 

Practice makes perfect- it also makes money. Michael Jordan and his teammates knew it, and the best IT teams in the world know it. Take your team's performance to championship levels with the right processes and the right tools- and, if you need help, think of Praecipio Consulting as your coach with a lot of championship experience. 

 

About Sam Besozzi

Sam is a Consultant at Praecipio Consulting where he delivers expert solutions to our top clients. He has an extensive background in process improvement and design and draws heavily from Six Sigma, Lean, and other efficiency-focused models. As a new Austin, TX transplant (originally from Ohio), Sam enjoys exploring his new hometown, hiking, and searching for the perfect taco.

Topics: atlassian case-studies blog analysis best-practices business experts implementation process process-consulting technology workflows support configuration consulting-services itil itsm jira-service-desk request
2 min read

Praecipio Consulting Webinars

By Praecipio Consulting on Dec 20, 2012 11:00:00 AM

Our monthly webinars are designed to help you become proficient with the entire Atlassian product suite. Wether you want to convince your team to adopt Jira or are in search of some handy tips and tricks for End Users and Administrators, our webinars are designed for any skill level.

 

Praecipio Webinars

Topics: jira atlassian efficiency management practices process tips tricks lifecycle
5 min read

Collaboration Best Practices - 3 Reasons Why Email Hurts Your Productivity

By Praecipio Consulting on Dec 12, 2012 11:00:00 AM

The following content was taken from Atlassian.com:

One of the turning points for communication in the workplace was the invention of email. Historically it’s been the easiest way to make contact in any business relationship – short, pointed conversations with the teammates you work closest with, or quick messages to people you’re communicating with for the very first time. You could say it changed the way we all work. Since its inception, however, the notion that email is also a good channel for team collaboration is what’s holding us all back.

Email is great for communication, but not collaboration…

 

Email is an effective means for communication, but when it comes to collaborating with your team on projects and getting work done, it’s a major hindrance to your team’s productivity.

  • Group conversations grow unwieldy too quickly
  • Keeping track of the most current version of an attached document is the modern-era’s needle in a haystack
  • It’s nearly impossible to maintain clarity about what needs to get done, and by whom

At the end of the day, when it comes to collaborating with your team, email wastes A LOT of your time.

Don’t get us wrong, email is not all bad. It’s really effective at quickly and effortlessly communicating with others, but it just doesn’t scale. When it comes to productively working together with your team, it fails to help you get the job done. Here are three reasons why we feel email is killing your productivity.

1. Your email inbox is a lot like quicksand

You receive a ton of email each day (yeah, like you didn’t already know that!) – some of it’s important, some actionable, some is SPAM, and some is unavoidably pointless. As a result your mornings go wasted in your attempt to reach inbox-zero. It’s a losing battle. Each time you take a step forward, you take two back. You’ve likely tried all the organizational features your email client has to offer to control your inbox – labels, filters, multiple inboxes, smart inboxes – but at the end of the day, your morning consists of at least an hour of unavoidable email ground-and-pound. You also probably manage emails when you get home at night and even first thing in the morning when you wake up just to keep your head above water. I’m preaching to the choir here, right? The fact is that this is the norm these days and hardly leaves you anytime to get real work done.

Pro-Tip: Use the ‘Four D’s of Decision-Making’ model

According to a article published by Microsoft, of the email you receive:

  • 50% can be deleted or filed
  • 30% can be delegated of completed in less than two minutes
  • 20% can be deferred to your Task List or Calendar to complete later

With this in mind it’s good practice to decide what to do with each and every email you receive – you have 4 choices:

  • Delete it
  • Do it
  • Delegate it
  • Defer it

2. Your email inbox silos your team’s tacit knowledge

Email is regularly used to share and discuss work, but that doesn’t mean its supposed to. Attaching files and documents or linking to them via shared network drives makes for a complete mess. Countless versions of shared files and relevant follow-up conversations are trapped in email inboxes everywhere. Your inbox is a graveyard for valuable tacit knowledge, knowledge that gets buried deeper and deeper every minute of every day. It’s truly criminal.

So, what’s the real problem? Email is a tool that best serves simple communication, not discussion, and certainly not collaboration either. When you send an email asking someone to review your work, the most valuable piece of information being transferred is not the file itself, but the ensuing conversation. Regardless of the fact that it’s incredibly difficult to find this email in your own inbox later, no one else outside of the email thread has the opportunity to benefit from this transfer of knowledge, keeping stakeholders in the dark.

3. Switching context between work and email wastes a lot of time

The rate at which most people check their email is astonishing – it’s practically become a nervous twitch. Just like Pavlov’s dog, your email has you trained incredibly well.

The problem with checking your email so much is that you rarely have a solid block of time to get any real work done. Take into consideration that if you’re actually checking your email 36 times an hour, and it takes 16 minutes to refocus after handling an incoming email, your workday is basically non-existent.

Switching contexts is distracting, if not annoying, and your email is the number one culprit – destroying the focus you need to get your job done well.

Pro-Tip: Practice Timeboxing to increase personal productivity

Thanks to email, staying on track at work is nearly impossible. Timeboxing is a time management technique that limits the time during which a task is accomplished. Start with 25 minute intervals. Work on a task for 25 minutes, take a 5 minute break, then commit to email for 25 minutes, and finally take another 5 minute break. Repeat. Focus. Flourish.

If 25 minutes sounds like a lot of email time, it sure beats checking your email 36 times in a single hour. At least with Timeboxing you can put all of your energy both into your work and email respectively.

Is there a solution?

We’ve outlined the major problems with using email to collaborate with your team, and even provided a few tips to help avoid the daily snags of collaborative emailing, but these are just simple workarounds. They don’t necessarily get at the core of your problems, which is that email is not the best solution for team collaboration.

OK, we are Atlassian Experts so we’re obviously biased, but we encourage ut clients to use Confluence and HipChat, Atlassian’s team collaboration and group chat tools, as means to reach decisions faster with less email and fewer meetings.

Topics: atlassian blog business confluence efficiency enterprise management optimization process project technology value collaboration information
1 min read

Praecipio Consulting - Atlassian Enterprise Expert

By Praecipio Consulting on Nov 15, 2012 11:00:00 AM

Along with Atlassian’s new offering of Enterprise level Jira and Confluence comes the Atlassian Enterprise Expert Certification. It’s designed to help Enterprise level clients find Atlassian Experts best suited to provide solutions to enterprise level problems. It’s hard to believe that it has been 6 years since our first enterprise deployment, and we are honored to announce that we are officially, Atlassian Enterprise Expert Certified!  

As an Atlassian Enterprise Expert, we have expert-level knowledge and success in the following:

  • Configuration,  analysis, development, and integration of large scale Atlassian installations
  • Diverse product experience with the entire Atlassian product suite
  • Hybrid tool chain experience with both Atlassian and non-Atlassian tools and their integration
  • Git, Mercurial and Subversion

Over the last 6 years, Praecipio Consulting has provided Expert Services to small, 5 person companies to large fortune 100 and 500 companies across several industries including the automotive, pharmaceutical, aerospace engineering, retail, gaming, and financial sectors. 

Topics: jira atlassian blog austin central business confluence efficiency management process technology texas value continuous-improvement information operations

Jira 5.2 Sneak Peek

By Praecipio Consulting on Oct 26, 2012 11:00:00 AM

The Atlassian team has been working hard, and to prove it here is a sneak peek of Jira 5.2, soon to debut. With Jira 5.2, it’s easy to add, remove and swap workflows to find the perfect set for your project. Check it out:

 

 

Learn more and let Atlassian know what you think at here.

Topics: jira atlassian blog business process product-services technology information it
3 min read

Jira Tip of the Month: Dot and Comma Dialogue Shortcuts

By Praecipio Consulting on Oct 3, 2012 11:00:00 AM

Dot ‘.’ and Comma ‘,’ shortcuts

Take your fingers off that mouse! These keyboard shortcuts will help you become a Jira speedster, and get your co-workers to ask “Whoa, how’d you do that?”

Dot Dialog

When your on the Issue Navigation screen or viewing an issue, pressing ‘.’Will bring up an operations dialog menu.

From here, start typing the first few characters of the operation you wish to use.  For example, if you are viewing an issue and want to close it, simply type ‘.’ then ‘close’.

Here is a list of operations you can access using the dot dialog:

  • Start Progress — Set the issue’s Status to In Progress.
  • Resolve issue — Set the issue’s Status to Resolved and select the appropriate Resolution.
  • Close issue — Set the issue’s Status to Closed and if the issue has not already been Resolved, select the appropriate Resolution.
  • Reopen issue — Set a Resolved or Closed issue’s Status to Reopened.
  • Edit — Edit the issue’s details (Summary, Description, etc).
  • Assign — Select an asignee for the issue.
  • Assign To Me — Assign the issue to yourself.
  • Comment — Add a comment to the issue.
  • Log Work — Record the work done and time spent on the issue. This option is only available if Time Tracking has been activated on your Jira site.
  • Attach Files — Select a file, upload it and attach it to the issue.
  • Attach Screenshot — Select a file, upload it and attach it to the issue.
  • Voters — Opens the Voters list of the issue, where you can manage your vote and see others who have voted on the issue too.
  • Add Vote — Adds your vote to the issue. (This option is only available if you did not create the issue.)
  • Watch Issue — Become a watcher of the issue.
  • Stop Watching — Stop watching the issue. (This option is only available on issues you are currently watching.)
  • Watchers — Opens the Watchers List, where you can manage watchers of the issue.
  • Create Sub-Task — Create a new issue which is a sub-task of the issue.
  • Convert to Issue — If the issue is a sub-task, convert it to a standalone issue.
  • Convert to Sub-Task — If the issue is a standalone issue, convert it to a sub-task.
  • Move — Move the issue to a different project.
  • Link — Create a link between the issue and another issue. This option is only available if Issue Linking has been enabled on your Jira site.
  • Clone — Create a new issue which is an identical copy of the issue.
  • Labels — Edit the issue’s labels.
  • Delete — Permanently remove the issue.

(Note that some options in the menu will only be available if the operation is relevant to the issue, if you have the necessary permissions, and if certain features have been enabled by your Jira administrator.)

Comma Dialog

Similarly, if you are viewing an issue, pressing ‘,’ (available in Jira 5.1 or greater) will bring up the Go To Field popup.

Use the popup to edit issue fields in-line, without leaving the page. The following fields are available for editing:

  • Assignee
  • Summary
  • Issue Type
  • Priority
  • Component/s
  • Affects Version/s
  • Fix Version/s
  • Reporter
  • Description
  • Labels

Tune in next month

We’ll be delivering you tips and tricks every month, so make sure to keep you eyes peeled next month for another handy Jira tip. If you found this helpful, please visit Atlassian University - interactive tutorials and videos with tons of tips just like this one.

Topics: jira atlassian blog business efficiency management process tips tricks lifecycle
2 min read

Jira: Not Just for Software Development

By Praecipio Consulting on Aug 17, 2012 11:00:00 AM

Jira’s an issue tracking application, but its core flexibility and strengths mean it can become much more than a tool limited to a development group. Jira’s incredibly adept at helping teams track and accomplish tasks. Jira also has a masterful ability to manage life cycles - and it’s found great success in numerous use cases.

Use Cases

The following use case guides are meant to explain a bit of the details related to using Jira for a specific use case. The info you’ll find in here highlights much of what we’ve learned from working with clients in a variety of different industries, as well as our internal expertise and use of Jira.

For each of these use cases, we’ll attempt to highlight:

  • Particular Jira functionality specific to the use
  • Related plugins we’re aware of
  • Customization and tweaks
  • …and sometimes a sample file to help get you started

General and Non-Software Uses

Agile Software Development

Project Management

HelpDesk / Support / Trouble Ticketing

Test Case Management

This can be done by using either of the following approaches:

Requirements Management

Change Management

Topics: jira atlassian blog scaled-agile austin automation business efficiency enterprise issues management process services technology value tracking change cloud collaboration computing continuous-improvement incident-management information integration it itil itsm operations
6 min read

7 Ways Social Enterprise Apps Are More Than Just Talk

By Praecipio Consulting on Aug 1, 2012 11:00:00 AM

by Ashley Furness

CRM Market Analyst, Software Advice
June 27, 2012

Until recently, I might have called Microsoft crazy to drop $1.2 billion on social enterprise app vendor Yammer. The business case for replicating popular social networking functionality in a corporate environment seemed dubious at best. Would there ever be a return on investment?

“Social is more than a trend, it is a revolution that is changing the way we work and collaborate. Powerful social tools, such as Chatter, help employees work faster and more efficiently—making it a strategic piece of the workforce.” — Dave King, Chatter Product Marketing Director

But then I talked to some corporate AtlassianYammerChatter and Jive users, all of whom claimed measurable gains from these tools in a variety of areas. Here are seven ways they derive value from social enterprise applications.

1. Streamline Project Management

Software developers at PerkStreet Financial use Yammer to facilitate scrum meetings, a key component of the agile software development methodology. Rather than hold their daily morning standup meetings in person, each member of the 37-person team posts “what I did yesterday,” “what I will do today” and “barriers to moving forward” using the hashtag #scrum.

Praecipio Consulting has helped in.gredients, a package free micro-grocer, leverage many of Atlassian’s products into extremely powerful tools for project management. Jira and Confluence for example, are used in conjunction to inform teams or others externally on goals, tasks, progress, and results. Confluence makes it easy for their teams to collaborate and share knowledge of Jira roadmaps, workflow, and tasks, or to document work, allowing users to delegate tasks with the “@”symbol.

The tag in Jira and Confluence allows users to quickly see what everyone is working on and chime in when appropriate. Similarly, Yammer can also delegate tasks to others with the “@” symbol. With Jive, users can also employ shortcuts such as an “!” to pull information into the thread from CRM and other enterprise systems.

2. Augment Transparency and Accountability

Since PerkStreet hosts all conversations on Yammer rather than trapped in someone’s inbox, management has continuous insight into the team’s progress.This also prevents work duplication and redundancies because everyone is literally on the same page.

“If you look at someone’s scrum over time, you can see whether they actually accomplished what they said they were going to,” PerkStreet COO Jason Henrichs notes.

Similarly, Jira and Confluence have allowed for Praecipio Consulting to increase its clients’ transparency and accountability even in the case of telecommuting among employees, who at times live in different states. Christian Lane, Managing Partner of Praecipio Consulting said, “the ability of the Atlassian product suite to increase transparency and establish accountability has allowed our business to grow and operate seamlessly across borders.”

3. Increase Communications Efficiency

HipChat, the newest member of the Atlassian family, is similar to Yammer and Jive. It’s a hosted group chat service that helps teams, or entire companies, collaborate in real-time. HipChat has a powerful API and comes loaded with integrations to Atlassian’s most popular products - JiraConfluenceFishEye and Crucible. These integrations allow you to get targeted notifications from products into the relevant chatrooms for your teams.

Salesforce surveys show enterprise wikis can reduce email by 30 percent and meeting by 27 percent.

FlexJobs founder and CEO Sara Sutton Fell said Yammer drastically cut down on her need to email, call or schedule a meeting to check in.

4. Find Experts Faster

Centerstance Inc. Managing Partner Greg Lueck says Chatter helps sales staff answer deal-specific questions expeditiously. He recalled one situation where a partner needed someone certified in Cast Iron software integration who spoke Mandarin. The resource manager working with the partner posted the query in Centerstance’s news feed.

“They had an answer within 30 seconds… in Mandarin,” Lueck remembers. In this and similar scenarios, the employee would have otherwise “relied on a central repository of all company’s experience that is located in one person’s head, or nowhere at all.”

Jive surveys show sales win rates increase an average of 23 percent, and time to find experts falls 34 percent.

5. Better Leverage Information and Insights

Social enterprise vendors have invested heavily in social and adaptive intelligence. These sophisticated algorithms suggest articles, files and experts based on the user’s position, connections, group memberships and resources they’ve previously accessed.

“Chatter knows what you care about based on your activities, making it’s value immeasurable,” King says of Chatter, the salesforce.com social layer. As a result, employees are better informed and can answer questions before they even know they have them.

“Imagine you have 10,000 people in an enterprise. Sales materials, RFPs are constantly flowing through system… Jive makes the most of this information by channeling it to the right people,” according to Jive Product Marketing Director Tim Zonca.

Additionally, HipChat stores full conversation history, so anyone new that joins a room can catch up and participate in the discussion.

“HipChat is incredible – perfect for product teams but fantastic for any team. Its use absolutely exploded at Atlassian, demonstrating the viral adoption potential of a modern communication system for teams,” says Mike Cannon-Brookes, CEO and co-founder of Atlassian. “Connecting and sharing ideas in real-time helps teams move faster, and HipChat does this better than any other product I’ve used.”

6. Generate More, Better Ideas

Yammer provides several means for employees to contribute ideas–from responding to queries and surveys, to posting ideas in a group discussion threads. Users receive gratification when co-workers and leadership “like” their contribution. Then, they are continually rewarded as they watch project teams bring the idea to fruition.

With one advertising campaign, for example, Deloitte CEO Peter Williams asked employees for their ideas for a tagline. More than 38 groups formed that submitted 1,184 original concepts.

7. Boost Employee Recognition and Engagement

In the four years since Deloitte AU implemented Yammer, the turnover rate for active users has fallen to two percent annually–about 10 times less than for employees who don’t use it. Leadership attribute change to employees feeling more engaged and recognized for their work.

“In a company with 180,000 people, most employees rarely interact with leadership,” says Frank Farrall, national leader for Deloitte Australia’s Online Consulting Practice. “Yammer breaks down those barriers.”

Deloitte leadership uses Yammer to pull reports that identify employees with high engagement and positive feedback. The more a user interacts with groups, downloads articles and responds to queries with the same keywords, the more they are distinguished as thought leaders on a subject.

“This is one key way to rise up in the firm–get recognized as someone who drives connectivity,” Farrall added.

Deloitte layered gamification elements into Yammer to further drive engagement and recognition. Using the behavior platform Badgeville, Deloitte awards “badges” when employees report milestones in Yammer, such as completing segments in Deloitte’s Leadership Academy. Users can monitor their rank on a leaderboard that shows what they need to do to surpass the person immediately ahead, encouraging them to do more.

 

Topics: jira atlassian blog business confluence efficiency enterprise management practices process tips tricks value collaboration continuous-improvement operations
2 min read

The Powers of Persuasion - Atlassian and Business Process Management

By Praecipio Consulting on Jul 26, 2012 11:00:00 AM

During our last Atlassian User Group meeting a few attendees asked us for pointers on how to convince their managers to implement or expand upon the Atlassian product suite as a Business Process Management Tool. To us the task seemed easy, especially since Process Optimization and Management are some of our founding principles.

After doing a bit of research we were a bit surprised by what we found. According to a study conducted by the Journal of Information & Management71% of executives had negative feelings concerning IT as a source of competitive advantage.

This is especially shocking since exploiting current capabilities while simultaneously developing new ones is a common theme among organizations. This idea serves as a baseline for strategic management and is crucial for adapting to changing environments. It’s through this delicate balance of business activities that the notion of Business Process Management (BPM) was born.

As BPM continues to be considered an important way for organizations to achieve a competitive advantage, senior management should be aware of IT’s ability to facilitate these processes. However, as the study pointed out, this isn’t always the case. In many organizations senior management’s reluctant to promote the strategic role of IT and instead, consider it just an automating tool.

This notion’s not only outdated but it also negates the entire philosophy of BPM, and the idea of developing new organizational capabilities.

So how can you overcome these seemingly insurmountable sentiments, standing in the way of cost-cutting, Business Process Optimization? According to the study, executives were most likely to be convinced of the almighty powers of IT when provided with substantial evidence of the following outcomes:

  • Assurance in the success of process re-engineering
  • Greater simplification in business process
  • Increased efficiency by at least 50%

So whether you are attempting to convince a coworker, boss, or yourself, being well armed with relevant examples of the above will come in handy.

Looking for relevant examples? Try the following case studies:

Topics: atlassian blog automation bpm business management practices process tips tricks continuous-improvement lifecycle operations
5 min read

Meet the New & Improved Bamboo OnDemand!

By Praecipio Consulting on Jul 17, 2012 11:00:00 AM

If you’re a Bamboo OnDemand subscriber, you could be forgiven for feeling a stab of jealousy every time a new batch of awesome features comes out for the on-premises Bamboo offering.  ”When, oh when, will it be my turn?”, you pined.  Well, if you logged into your Bamboo OnDemand instance this morning, you already know that the wait is over.   Bamboo OnDemand is now roughly on par with Bamboo 4.1.  ”Roughly”, because there are still a few differences such as not being able to install plugins or use commercial version control systems.

The collection of features now available in Bamboo OnDemand is large enough to fill a book (regular readers know I’m not one for brevity!).  My strategy here today is to call out the biggest n’ bestest of ‘em, and point you to resources that’ll take you deeper in. So bookmark this page.  Reference it.  Love it. Repeat.

Better AMI Support

You’ll need to update custom any custom AMIs used by your build agents to make them compatible with today’s upgrade, but going forward this won’t be necessary.  In addition, BoD now offers a stock image for building on Windows as well as support for EC2 spot instances.

Read more about AMI & Agent Support here: Atlassian OnDemand Release Notes – July 2012

DVCS & External Repo Support

 

The people have clamoured for it, and so the people shall have it!  BoD can pull code from external Git and Mercurial repos hosted on Bitbucket, GitHub or on your own network.  That goes for SVN repos on your own network, too.  Using Git submodules?  No problem. Want to pull code from a hosted SVN repo and a Bitbucket Mercurial repo into the same build? Done.

Read more about DVCS & multiple repo support here: What’s New in Bamboo 3.3

Tasks

All your builders and post actions are belong to us Tasks.  Tasks are the granular steps that make up your Plan: checkout source code, call MSBuild, execute a script… etc.  Your existing builders were converted to Tasks as part of the BoD upgrade, and we think you’ll find it to be a great usability improvement.

Read more about Tasks here: Configuring Tasks

Manual Stages

Many users’ workflows require a set of requests and approvals for deploying code to an environment.  And many many users would like to compile, test and deploy to a QA env with each commit –but deploy to production much less frequently.  Manual stages let you construct a single pipeline, and add “gates” or “valves” to satisfy those use cases.  You’re welcome. 

Read more about Manual Stages (and other cool features) here: Bamboo 3.2 Release Notes

Plan Branches

For a couple of years, the developer community has been complaining that using short-lived branches to build new features simply doesn’t play nicely with continuous integration.  We’ve taken a big step toward proving them wrong.  As soon as Bamboo knows there’s a new branch in your repo, it will clone any associated Plans and point them at the new branch.  Branches are automatically discovered in Git & Mercurial repos, with auto-discovery for SVN coming soon. Très facile!

 

Automatic Merging

Because automatic branch discovery wasn’t enough.  We wanted more!  With each commit to a branch, BoD can now grab code from a second branch, merge the two, run your Plan against the merged code, and if successful, push the merged code to either branch.  Great for ensuring longer-lived branches don’t drift to far from the main line, or for two developers collaborating on a feature using their own feature branches.

Read more about Automatic Merging here: Using Automatic Merges

Test Quarantine

When I was a test engineer, I would’ve killed for this.  But you don’t have to!  No more commenting out tests or dorking around with your suite.xml file.  Just click a button to neutralize a busted test.  It’ll still get run so you can see when it’s fixed, and you’ll see your count of quarantined tests on each build result summary so you don’t loose track of them.

Read more about test quarantine here: Putting Tests in Quarantine with Bamboo 4 (Yes, the zombie apocalypse has indeed arrived.)

Jira Issues

BoD has issues.  And how!  Forget all that inefficient context switching, and create Jira issues from any build results page in Bamboo.

Read more about Jira Issues here: Top 5 Reasons Creating Jira Issues from Bamboo Makes Your Team Awesome-r

Broken Build Tracking

Team leads and scrum masters have better things to do than hound people to fix the build.  With broken build tracking you can assign one person to be the default owner of broken builds for each Plan, or have responsibility assigned to users who made changes since the last passing build.  Bamboo will nag them on your behalf until the build is green again.

Read more about Broken Build Tracking here: Bamboo 4.1 Announcement Blog

Failed Stage Do-Overs

Everyone needs a do-over sometimes.  Maybe a build config needed tweaking.  Maybe your QA environment down just as you were deploying to it.  Re-running only the Stage that failed can save you a whole lot of time.  And time is money, so… yeah.

Read more about Failed Stage Do-Overs here: Bamboo 3.2 Release Notes

Onward!

Bamboo OnDemand is now resting on a more stable platform than before, so expect fewer stability hiccups going forward.  We’ve also made custom AMIs for your build agents easier (even updated the templates, so you might not need to customize at all!), and made Windows images available by default.  Très facile (redux).

But it’s also the end of an era.  This is the last announcement I intend to write about BoD upgrades.  Why?  Because they simply won’t be a big deal anymore.  We’ve retro-fitted our upgrade process such that BoD will be upgraded with new versions of Bamboo at the same time, possibly even before, those versions are available for installation behind your firewall.  This is one “good bye” I think we’re all happy about!

Topics: atlassian blog bamboo business enterprise management practices process technology collaboration information it lifecycle

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

In need of professional assistance?

WE'VE GOT YOUR BACK

Contact Us