3 min read

Agile vs. Scrum - What's the Difference?

By Rebecca Schwartz on Aug 19, 2021 10:03:00 AM

Blogpost-DisplayImage-August-Agile-vs-Scrum-Methology- Whats-the Difference-

Organizations are rapidly moving toward new work management styles, especially in the age of digital transformation. If you work in project management, you've probably heard the term "Agile" at some point in your career. Maybe you've considered taking this approach with your teams, and have already done some research. "Scrum" is another term you've most likely heard during your research. Although this is a term used in rugby, it is also a specific methodology teams use to work in an Agile manner. At Praecipio Consulting, we've assisted many teams 

with their move to Agile, using the Atlassian toolset to support and ease their journey. We've also worked with many teams who use Scrum specifically, but many use different frameworks - using Scrum is not a requirement to be Agile. Let's take a moment to understand the difference between Scrum and Agile.

What is Agile?

Agile is a project management style in which organizations use an iterative process to continuously deliver work while consistently receiving and incorporating feedback throughout the process. Flexibility is key, so teams can quickly adapt to market changes and customer needs. Agile has a set of principles and values organizations are expected to follow, laid out in the Agile Manifesto. The Agile Manifesto does not delve into specific practices and activities teams should follow in order to work in an Agile way: it serves as a north star for organizations to align to in their Agile journey. There are a few Agile frameworks teams can use to work in an iterative manner, such as Scrum and Kanban. Agile puts an emphasis on people over processes and tools, and gives autonomy to the people on those teams. With that being said, it is up to the teams to decide which framework works best for the way they work and the work they're delivering. 

What is Scrum?

Scrum is one of the many frameworks teams can use to work in an Agile manner. It is mainly used by software development teams, and relies on time-boxed iterations called Sprints. Sprints are made up of the work developers commit to completing within that iteration, typically 2 weeks. The work scheduled in each sprint is based on priority and team capacity, and is carefully estimated to ensure teams can commit the work they've delegated to the sprint. This framework is very detailed, and prescribes a set of specific roles and events, including:

  • A Scrum Master, who protects the teams and ensures they are able to do their work without impediments.
  • A Product Owner, who manages and grooms the product backlog ensuring the anticipated work aligns with the needs of the customer and business.
  • The development team who actually complete the work in the sprint.

As I mentioned above, Scrum is a way teams can work if they're on their Agile journey, but it is not the only option. There are other Agile frameworks that may work better for teams.

How Do Agile and Scrum Differ?

Now that we know a bit more about Agile and Scrum separately, it's easier to lay out the differences between the two. Agile is more of a general philosophy that paints a broader picture around working in an iterative, flexible manner. Scrum is a specific Agile framework and is more granular than Agile. Although both rely on iterations: in Scrum they're specifically time boxed and called Sprints. Scrum also prescribes specific roles and ceremonies, while Agile focuses on the overall principles in the Agile Manifesto. Scrum is also more focused on the team level and the delivery of work. Agile can be scaled across an organization using other work frameworks such as the the Scaled Agile framework, or SAFe, as well as Large-Scale Scrum, styled as LeSS. 

With that understanding in mind, maybe you're ready to start your Agile journey! The Atlassian tools, such as Jira and Confluence, are built to support Agile and the specific frameworks. Jira Software makes it easy to get started with Scrum by providing an out-of-the-box Project template. At Praecipio Consulting, we focus on ensuring the Atlassian tools facilitate your Agile journey by implementing best practices and incorporating our extensive experience working with Agile teams. Reach out if you have any questions around Atlassian and Agile - we're here to help.

Topics: blog kanban scrum project-management safe agile frameworks less
3 min read

What is Jira Align: A Primer

By Amanda Babb on Jun 30, 2021 4:45:59 PM

Blogpost-DisplayImage-June_What is Jira Align- A PrimerA couple of years ago, in Atlassian's annual flagship event formerly known as Summit and now known as Team, I was in a room full of people for two days providing training on Advanced Roadmaps for Jira on behalf of Atlassian. If you've never attended a live Summit event, the Kickoff Keynote is always a sight to see. One year, Scott and Mike dressed as Daft Punk and mixed music as DJ Kanban (I still nerd out on that one), you see announcements about the expansion of Pledge 1%, and, of course, new product announcements. Jira Align was acquired by Atlassian and announced at Summit 2019. I. Was. Floored. You see, we here at Praecipio Consulting were looking for a larger agile-at-scale solution for some of our largest clients. 

Enter Jira Align

After becoming a SAFe® Program Consultant (SPC) in 2015, I spent a lot of time with clients understanding intake and execution processes and facilitating them through the Atlassian product suite. These clients were either just starting their SAFe® journey or had been the earliest adopters and already implementing SAFe®. After implementing Advanced Roadmaps (then known as Portfolio for Jira) to support SAFe®, becoming the Atlassian University On Demand "voice" of Planning with Advanced Roadmaps, and guiding the course content with Atlassian, I was in love with Advanced Roadmaps. And I still am. Advanced Roadmaps is a powerful data aggregation, roadmap, and scenario planning tool for small- to medium-size organizations either as standalone entities or within an Enterprise organization.

Jira Align, however, brought forth a whole new realm of possibilities. Bringing robust framework expertise and combining it with an easy-to-use interface, Jira Align is THE solution for Enterprise organizations running agile-at-scale. Don't believe me? Atlassian is considered a Leader in the Gartner Enterprise Agile Planning Tools Magic Quadrant as of April 2021. Experience and third-party accolades aside, why is Jira Align so amazing? Let's take a closer look. 

Jira Software Integration

Unlike Advanced Roadmaps, Jira Align is a standalone product hosted either in multi-tenant or single-tenant cloud infrastructure. While there is an on-prem solution, of course, there are a lot of additional considerations if you have to choose this deployment. The connection between Jira Align and Jira Software supports both Data Center and Atlassian Cloud instances. The most critical part of the integration is the Jira Software Epic. Epics can be created in Jira Align and pushed to Jira Software or created in Jira Software and pulled into Jira Align. Keep in mind, when creating the integration, best practice is to isolate Epics into their own Jira project. Bringing in Stories and Sprints is also easier if a Jira project represents a single team. 

Rooms at Every Level

Whether you're just starting out with a single Agile Release Train (ART) or are running multiple ARTs, Jira Align provides the Program Room for each ART. This is the central hub for tracking the current Program Increment (PI) and planning the next one. Sprint Progress, investment runway, intra-ART and inter-ART dependencies, PI Burndown, it's all centralized within the Program Room. This provides Business Owners, RTEs, and Program Managers a clear view of the progress of the work in the PI. 

Jira Align also provides the Portfolio Room and Strategy Room. These rooms provide the progress towards Strategic Themes, Portfolio investments, progress toward long-term goals, and status updates. When properly connected to Epics in the Program room, Teams and ARTs can open the "Why?" tab on the Epic and see how their work is contributing to the overall strategy. 

Everyone's Favorite: Reporting

Jira Align has over 180 out-of-the-box reports. Each layer in Jira Align has a Track section pre-populated with the more popular reports for that section. For example, in the Program section, Jira Align provides Program Increment tracking, Program Increment insights, and Dependency Maps. If you're not sure what type of report you're looking for, simply click the Reports menu and ask a question in the search box. 

For those organizations that need to integrate with other systems or need more robust business intelligence, Enterprise Insights can be added to Jira Align. 

Want to know more? We here at Praecipio Consulting would love to walk you through how Jira Align can support your agile-at-scale transformation. Contact us!

Topics: atlassian blog scaled-agile integration reporting jira-align safe advanced-roadmap
7 min read

SaaS can be SAFe®

By Christopher Pepe on Dec 11, 2020 2:30:00 PM

Blogpost-display-image_SaaS can be SAFe Blog

SaaS is the future

2020 has caused the world to work from the internet. Whatever you used to do in your own data centers can now be performed by vendors, be they cloud or software service providers, better, faster, more securely, and at less cost than you.

The diagram below indicates the trajectory of change from traditional to SaaS (software as a service). Learning how to manage SaaS providers is the new skill that must be learned and introduced into your strategy.

Screen Shot 2020-12-05 at 10.03.18 AM

The hardships of this year have also proven that you need agility in your 5 year plan so that you can change along the way.  The capability to pivot based on circumstances is the other new capability of an organization moving towards a digital and VUCA (Volatility, Uncertainty, Complexity, Ambiguity) future. You have to be agile, not just in IT, but the way you think, act, and react. Leadership has to manage and accelerate this change in culture and behavior, which means scaling new ways of working enabled by technology is the new management paradigm.

Allowing a SaaS provider to manage a core function such as Marketing, HR, or Sales is the norm, freeing you to concentrate on creating unique services that benefit your customers and save time for your staff. 

Scaled Agile Framework SAFe®

No matter what blend of Agile that you are using (Scrum, Kanban, DevOps, AgileITSM, XP, TDD, BDD, etc.), you will need to spread these practices across your business. New ways of working, constant improvement, collaboration, and the elimination of siloes, benefitting from technology, be it your own or others, is the only way to survive. 

Accomplishing this change means a dramatic, and in some cases, drastic, alteration to how things are currently performed:

  • You keep your program office but lose your project mentality
  • Product and Service Owners are the new organizational role with accountable budgets and teams
  • Agile Budgeting replaces annual budgets, and the same occurs to annual reviews as constant and consistent feedback is provided top-down
  • Multi-year contracts are swapped for partners that facilitate your agility
  • The use of technology to keep you in business enables every aspect of your business
  • Staff are not made redundant but instead acquire t-shaped skills
  • Customer focus and shifting left from their request or needs drives your product strategy

Organizations need guidance to make these types of change successfully. Enter Scaled Agile Framework (SAFe®).  The diagram on their website visualizes the breadth of their philosophy and impact on an organization. 

SAFe® is a continually changing set of practices that has blended the technology, people, and business practices into a competency-based model: 

  • Leadership based on agile and lean: empowerment, self-organization
  • Team and Technical Agility: No defects, use of cloud & internet, open-source, SaaS
  • Behavior-Driven Development (BDD): products based on the people use them
  • Test-Driven Development: code, infrastructure, people feedback in short cycles
  • Agile Product Delivery: small changes made often, usually daily
  • Lean Portfolio Management: if it is not helping someone, then you don’t do it, constant improvement, reduced technical and cultural debt
  • Lean Governance: common or standard data models, budgets are based on the value of outcomes and funded accordingly, guardrails guidelines both corporate and regulatory, business continuity and sustainability is a daily way of acting 
  • Organizational Agility: long-term goals but very short-cycle plans capable of pivoting based on breaching a KPI or OKR (Outcome based vital indicators)
  • Continuous Learning Culture: effort is rewarded, management changes to a coaching model from a telling model, relentless improvement is mentored, innovation is the goal

SAFe® is the most ambitious version of this framework's scaling technology, leadership, financial, and organizational practices. It supplies examples, training, templates, and a worldwide community of practitioners. It is not for everyone. It is not a program of introducing Safe® that will make it successful for you but instead a multi-year effort of scaling the way your business does things at every level into a new model. 

SAFe® helps you avoid and overcome these engrained practices:

  • Budgets by department or project become funding for products and services
  • Prioritization of new features or services is based on value of delivery and cost of delay
  • Creating your own software is replaced by using open source or SaaS
  • Data used and kept by your business is standardized for ease of maintenance and change to new services as needed
  • Mapping the way you work end-to-end and ensuring any changes are not localized but instead improve the flow of work and data is the new program office structure.
  • Change Approval Boards or freezes are stopped because you trust the testing and release process that has been enhanced and automated. 
  • Design thinking is encouraged to solve problems
  • Design thinking underpins making things as small and as standard as possible such that any part of your business can use it or improve it
  • Everyone is thinking about what can I do to make things better, do things faster and safer, and how can I save effort or time or money

SAFe® Benefits

  • Increase the velocity of change: ways people work and the software that supports these changes
  • The software lifecycle of Demand-Approve-Develop-Integrate with other code-Unit Test-Performance Test-Submit to Live Approval-Go live is replaced with Experiment-Develop-Test-Go live
  • SaaS + Cloud + Digital is the technology trilogy whereby owning your own technology is discouraged (still allowed where regulatory mandates leave no other option)
  • Complex projects requiring months or effort are replaced by an understanding of what a new service or feature or technical update will provide a customer or staff member and therefore, this is what is created and deployed
  • Technical stability is more critical than new service introductions (think of your customers and how angry they get when things go wrong)
  • Feedback, monitoring, alerting are the trilogy of information collaboration and coordination (no silos)
  • Legacy infrastructure or technical debt is mitigated by using cloud services aligned with your work and customer practices. Technology underpins the way you do things and not just there because!
  • Training on SAFe® culture and practices is top-down and extends to your external suppliers
  • Project Management is now Agile Product Management, coordinated across products and services instead of merely helping a department or team
  • Prioritization based on what it fixes, how it meets a regulatory demand, what outcomes it being in terms of value and customer satisfaction, or how it helps staff perform a function

Doing SAFe® means:

  • You are willing to release small chunks of change daily versus large pieces that might wait months before going live
  • You can monitor the impact of that change in terms of issued caused or customer satisfaction
  • If an issue ensues or satisfaction is not as expected, then you can easily roll-back the change with minimal effort or impact (go back to the way things were before)
  • New skills of negotiating or always thinking of enhancing products via technology are taught in a variety of formats such as hackathons, formal training, a partner working, and management coaching
  • Operating and Strategy long-term plans are replaced by short-term vision plans that are customer and market-centric
  • Centers of Excellence or Software Factories are created aligning how people working based on data and technology mapping exercises with the approved practices of the organization, which encourages:
    • Standard tooling for Enterprise Application/Service Lifecycle Management 
    • Standard data and artifact repositories
    • Use of SaaS providers for core activities
    • Always on testing, monitoring, and alerting across the value chains

A train yard is a frequent analogy to explain software factories and centers of excellence. You need a standard gauge rail for all trains to use, and an aligned place for trains to be monitored and dispatched. This allows trains to move safely across the landscape, delivering people to their locations. Your organization needs to establish the same kind of software delivery practice. This model is what SAFe® uses to foster the fast and safe distribution of technology via an engineered flow of work.

SaaS Safe® tips

  • Create a vision of why SaaS and Safe® are being adopted, underpinned by training
  • Change the language used top-down from project to product
  • Have metrics that make innovation for customers or staff the prime target
  • Developers develop and operations keep things up is the most prominent IT silo. Break this by making product teams that own their product or service.
  • Technology metrics of Defect Rejected Ratio, Detected Defects, Change Time compared to Market release, Value of Delivery versus Effort are viewed on product boards
  • Create fun programs of change such as Kill the CAB, which force the introduction of standard technology components for use by any aspect of the business
  • DevSecOps is not an option but a mandatory requirement: you have to test at every opportunity and use security practices and tools to keep your business safe and compliant
  • Automate what you can as often as you can, but only if this improves the quality and speed of work

SaaS is the way of allowing someone else to perform a function via the use of their technology. Carefully avoiding vendor lock-in will make SaaS a credible option for your business. The transition to remote working has opened up a world linked by technology, and your organization needs to do the same by scaling the thinking and practices of technology to everything you do. SAFe® is a framework proving your business a set of rules that promotes scaling Agile, Lean, and DevOps across your organization. It is a radical alteration of your culture that will take time and leadership to embed successfully.

Whether implementing SaaS, SAFe® , or just generally digitally transforming your company, Praecipio Consulting can help!

Note: SAFe® is a Registered Trademark via ©Scaled Agile, Inc.

Topics: scaled-agile saas safe agile
2 min read

How to Know If Your Organization Is Ready to Scale Agile: Tips & Best Practices

By Amanda Babb on Sep 28, 2020 12:15:00 PM

How to know if your organization is ready to scale Agile

Are You Ready to Scale Agile? 

You are an Agile evangelist. You have championed the shift to Agile at your organization and have coached several teams successfully. Your organization is delivering quality product faster to your internal and external customers. But there's still a struggle to coordinate across different parts of the organization. And you get pulled into meeting after meeting to coordinate across teams. As a result, your most successful teams are expressing frustration with each other and, and now, quality has slipped. Something has to change. 

You've heard about scaling Agile. You may even have an idea of some of the well-known frameworks, such as SAFe, LeSS, Scrum@Scale, etc. But are you ready? Is your organization ready to scale Agile? 

Organizational Readiness

While this is not an exhaustive list, ask yourself and your organization these questions to assess your readiness to scale Agile. 

  • Which framework is best for your organization?
  • Do you have management and executive buy-in? 
  • Do you have funding for external training and certification?
  • Can you group teams together to support strategic initiatives?
  • Can you identify your change agents and champions?
  • Can you identify a set of teams to pilot the change?
  • How much time are you willing to commit to the change?
  • How much time do you have to commit to the change? 
  • How much time are you willing to commit to continuous learning? 

Iterate Your Framework Implementation

Just like the scaled Agile frameworks themselves, you approach their implementation iteratively. One of our clients chose and implemented SAFe for a single program and scaled iteratively. They started with one Agile Release Train and in three years scaled to four Agile Release Trains with the intention to launch an additional train before the end of the year. They also reorganized the Trains once they realized they were no longer organized around value and instead were structured in a traditional resource-management way. 

The implementation of SAFe within this client's organization, while it had a specific start date, was implemented iteratively and over time. It also took the backing of management and executives and a devoted set of change agents willing to take the steps for scale.

We here at Praecipio Consulting have assisted our clients in their journeys to scale Agile. Let us know how we can help you take your first step. 

Topics: blog scaled-agile best-practices tips safe agile
1 min read

Is Going Agile Worth It? The Wall Street Journal Says So!

By Morgan Folsom on Jul 29, 2020 12:15:00 PM

2020 Blogposts_Is Agile Worth It- The Wall Street Journal Says So

Agile is one of the hottest trends in the business world right now - but is it actually worth it? (short answer: Yes!). The Wall Street Journal recently published an article that discussed the importance of cultivating an agile culture for enterprises who want to move forward with their business and survive the pandemic. Check out how our client, ACI Worldwide, has made impressive improvements in their process, pivoting to the Atlassian suite to manage their work across the board, in this Wall Street Journal spotlight. 

https://partners.wsj.com/atlassian/built-for-change/aci-worldwide-paying-agility-forward/

Not only did these changes help ACI Worldwide increase its enterprise agility, but it also successfully prepared their organization to quickly shift focus and resources during a constantly-mutating global pandemic. 

Give the article a read and let us know what you think!

Topics: scaled-agile enterprise service-management safe agile
3 min read

What is Customer Centricity in SAFe 5.0?

By Rebecca Schwartz on Jul 10, 2020 12:15:00 PM

2020 Blogposts_What is Customer Centricity in SAFe 5.0-

SAFe 5.0 puts a greater focus on the customer, placing them at the heart of all decisions around the product or service the business delivers. Although the technical and functional aspects of a product are key, the satisfaction of the customer ultimately decides the true fate of the solution. If the customer continues to have a positive experience, your business can continue to grow and thrive! In the updated SAFe 5.0 framework, Scaled Agile elaborates on Customer Centricity, which puts the customer at the center of all business decisions that guide an organization to not only meet customer needs but exceed them as well.

What is Customer Centricity?

Customer Centricity is the mindset that the business must adopt to provide a positive experience for the customer. With every decision business leaders make, how those decisions impact the customer must be at the forefront of their minds. For this reason, the organization studies market research and user insight to ensure they truly understand the customer's pain points and develop solutions to address them. Customer-centric organizations take new approaches to solving customer problems by using empathetic design, i.e. putting themselves in the shoes of the customer. In turn, the organization can fully engage with the customer and build long-lasting relationships with them. After all, this is what we try and capture in User Stories; however, in SAFe 5.0, we're capturing this information at every level of the organization to build the right solutions.

Why is Customer Centricity important?

Customer Centricity is important because customer satisfaction is the key to developing a business and maintaining it. If your solutions and services fail your customers, your business will also fail. This new focal point also matters because it allows organizations to get direct feedback and input from the customer. Listening to their ideas and opinions allows businesses to tailor the solutions to their exact needs, which increases company profits, attracts new customers, and enhances current customer relationships.

How does Customer Centricity Affect Me/My Organization?

As an individual and as an organization, this piece of the framework may change your mindset and the entire company vision when it comes to creating solutions. When in the decision-making process, whether on your own or collectively as an organization, the outcomes that affect the customer will need to guide those decisions. As an individual working on client solutions, you may sometimes get requests that aren't necessarily best practice. Using Customer Centricity, you can consult user and market research to arrive at a solution that is best practice while also satisfying the customer.

 

Our Thoughts on Customer Centricity

At Praecipio Consulting, we are excited about this emphasis on Customer Centricity, as we love providing an exceptional customer experience. While working on our projects, we gather customer feedback daily to ensure we're moving projects in the right direction. With this, we're also able to revise on an iterative basis, meaning changes are made consistently throughout the project, instead of piling up and causing delays at the end of the project delivery. We also find that this approach allows us to truly be customer-centric, as we are constantly engaging with the customer and strengthening our relationship with them. Internally, we keep a close eye on the updates to SAFe so we can practice it successfully, as well as guide clients through the changes as well.

 

If you are looking for more guidance on the SAFe's recent update and why it matters to increase your business agility, check out this post

Topics: scaled-agile safe customer-experience
6 min read

How Jira Align Helps Embrace Lean Budgets

By Amanda Babb on Jul 1, 2020 2:30:21 PM

2020 Blogposts_Lean Budgets in SAFe and Jira Align

Hopefully, you've followed my posts and webinars on Portfolio for Jira, as well as how to manage Lean Budgets in Atlassian and its ecosystem. We released a White Paper providing a solution for mid-sized organizations that have embraced SAFe® and want to also incorporate Lean Budgets concepts within the Atlassian technology stack. After all, one of the most critical pieces of adopting an agile mindset is to break the cycle of traditional Project Cost Accounting. 

Project Cost Accounting and agile frameworks (regardless of the flavor) are in direct conflict with one another. Moving teams to work in a Project Cost Accounting model does not work in agile frameworks. Instead, we move work to teams. When we scale agile, regardless of the model, all we're doing is connecting the overarching strategic initiatives to execution. Also, we're all still trying to figure out how to understand the costs associated with the work. SAFe® offers the seductive allure of Lean Budgets. Simply define the Enterprise budget and allocate it to the Portfolios to do what they will. Wait, what? Just hand over $100,000,000 to a Portfolio for the year and trust that they'll make the right decisions? As Yogi Berra once said, "In theory, there's no difference between theory and practice. In practice, there is." 

Lean Budgets Guardrails

While the Atlassian tools and ecosystem are not intended to be the financial system of record for any organization, one key part of Lean Budgets, which is called out several times in the Lean Portfolio Management competency in SAFe® 5.0, is to provide Guardrails. The four Guardrails are as follows: 

  1. Guiding investments by horizon
  2. Applying capacity allocation to optimize value and solution integrity
  3. Approving significant initiatives
  4. Continuous Business Owner engagement

© Scaled Agile, Inc.

The Atlassian tools, and specifically Jira Align, are uniquely positioned to provide the Guardrails for Lean Budgets. By adhering to the SAFe® Core Values of Transparency and Program Execution, Jira Align provides complete aggregation from the corporate strategy, including Mission, Vision, and Values, all the way through team-level execution and back up again. This includes Allocation, Estimate, and Actual comparisons based on the Program Increment. Mind-blowing, right? 

While you will have to wait for the full solution (details are coming soon), here are a few tips to assist you in your journey. 

Create a Strategic Snapshot

Your organization has a well-established Mission, Vision, and Values. They're likely plastered all over your organization's intranet or when in an office, you'll find them displayed every 25 feet down the halls. Add these into the Enterprise Room in a strategic snapshot that aligns with your fiscal year. Break down the Mission, Vision, and Values into long-term, annual goals and establish your Strategic Themes. Add those into Jira Align to start tying execution to these items.

Screen Shot 2020-06-24 at 10.03.55 PM

Themes are an entity in Jira Align. Think of them as an Issue Type that drives the rest of the hierarchy. However, one of the key strengths of Jira Align is ensuring, at every level, the entity is tied to execution. In SAFe® the key execution entity is the Program Increment (PI). Even if a Theme straddles several PIs, you must commit to the timebox of the PI. This drives the entire organization to say, "This thing is important to us, and this is how and when we plan on executing it." While at first, you may have no idea, you can always go back and add the information after the fact. 

Determine Theme Allocation for the PI

While you may not know the exact dollar amount while planning the budget, you've likely done the SWAG for the fiscal year. SWAG, of course, stands for Scientific Wild Ass Guess. As you're determining your Themes and Portfolio Epics for the Fiscal Year (or just your Themes), you will likely have a high-level idea of how much of the pie you will allocate to each Theme. Since they are also ranked by highest to lowest priority, the allocations should follow suit as well. If a Theme is ranked number one, it should have a higher percentage allocated than, say, Theme number 10. Theme allocations can be updated as your organization moves through the budget cycle. Jira Align will do the calculation for you as you determine the overall budget. 

However, to truly succeed at Lean Budgets in Jira Align, you must determine the budget for the PI. Again, as you're working through your organization's budget cycle, you can start with your SWAG. For example, if you have an overall budget of $100,000,000 for the fiscal year and your PI cadence puts you at 12-week PIs, then allocate $25,000,000 per PI to start. By tagging your Themes with the PI(s), you can start to understand the dollars, as well as the overall level of effort, needed for a specific PI. As you get closer to final budget approval, continue to refine these numbers. 

Determine a Blended Rate

While I've proposed a series of different methods for translating Story Points to dollars either via Cost Per Story Point or Total Cost of Solution or Monetized Opportunity Cost, the fact remains that we live in a time-based world (sigh). And our best method for translation still comes from determining a Blended Rate. In Jira Align, once you've determined the Blended Rate for the PI, you simply enter it into a field and the magic starts to happen. But how do we determine a Blended Rate? 

Remember, a fixed Team equals a fixed cost. Take the combined salary of the team members, divide it by workweeks, then divide it by work hours. You can skip a step if you remember the exact number of working hours are in a year, but that number will vary based on your geolocation. You can always adjust as needed based on PTO policies and holidays to determine the Blended Rate. From there, Jira Align takes over once you're in execution mode. 

Budget, Estimate, and Actual

In the Portfolio section of Jira Align, you can quickly access a report called Investment versus Actuals. Wait, what? It's that simple? I click a button, and I can compare plan, actual, and variance? That can't be right. 

To be honest, it truly is that simple. However, if Teams aren't fostering good data in Jira Software and if RTEs, Program Owners, Epic Owners, and the like, aren't making the connections in Jira Align, you will end up with junk. This leads to frustration, as well as low adoption levels of the solution. Take a deep breath, and remember Principle #1 of SAFe ®: Take an economic view. Just like any other tools your organization uses, you must adhere to the process and commit to the facilitation of that process within the tools. 

Based on the historical Velocity of the individual Teams in a Program, the Blended Rate, the Teams' Burn Hours, and the Theme Allocation, Jira Align will calculate the Estimate (original estimate at the start of the Program Increment) as well as the Actual (actual completed stories in each of the Sprints). This is where the Team discipline comes in. If Teams do not estimate work, move cards across the board, and close Sprints, this fails. You cannot calculate the roll-up, or if you do, it's wildly inaccurate. Thus, the comparisons are out of whack, and when compared against the financial system of record, you find that you've spent your time and money on Theme number 10 instead of Theme number one. 

Want to know more? 

In the coming days, Praecipio Consulting will release a White Paper detailing the solution to managing Lean Budgets with Jira Align. We look forward to your questions and feedback. Lean Budgets is still an emerging concept, and while we have a solid solution, we'd love to know how your organization is currently managing or where you are in your digital transformation journey with the Atlassian tools.

Topics: blog scaled-agile teams tips lean-budgets project-management jira-align safe
2 min read

SAFe Cheat Sheet: A Guide to Scaled Agile Framework

By Praecipio Consulting on Feb 23, 2015 11:00:00 AM

No matter the size of your organization or your industry, the end game of any company is to deliver the highest quality product to customers at the greatest market value, with the lowest cost of production. This school of thought drives the Agile methodology of software development, pushing for faster delivery of better products with the least amount of risk, and has fueled the scalable Agile solution for enterprise-level organizations: Scaled Agile Framework (or SAFe). Operating under the principles of Agile development, SAFe aligns the development and initiatives of all levels of the enterprise company- from agile teams to executives- for accelerated value delivery at a reduced risk. Leveraging short feedback cycles organized into sprints and release trains, the cost of deployment decreases as deliverables have clearer direction and requirements to ensure a better fit for purpose. 

How does Atlassian support SAFe?

What are the core values of SAFe?

 

How does Atlassian support SAFe?

The Atlassian product suite was created (and is continually innovated) to support best practices in the Software Development Lifecycle. To that end, the use of products like Jira Agile, Confluence and Jira Portfolio integrate to bring maximum traceability to every release, enabling teams to hit their deadline and their budget with the highest quality product. With Atlassian, you unlock the power of SAFe, leveraging Jira Agile, Confluence and Jira Portfolio to achieve the following objectives (and much more): 

Want to learn more about SAFe?

Ready to learn more about how Scaled Agile Framework brings best practices and greatest results to your enterprise organization? As Atlassian Platinum Enterprise Experts, we at Praecipio Consulting are here to help! First, check out our recent webinar on SAFe, Agile in the Enterprise, presented by Senior Solutions Architect, Certified Scrum Master, and soon-to-be SAFe Program Consultant Amanda Babb to get a more complete introduction to implementing Agile practices at the Enterprise level. Next, contact Praecipio Consulting to begin introducing SAFe to your company. We can assist you with anything from Atlassian product licenses, implementations and configurations (to get you the right tools for the job) to customized consultations and trainings on SAFe. 

Deliver your highest quality product and the lowest cost of deployment with SAFe, Atlassian and Praecipio Consulting!

Topics: jira atlassian blog scaled-agile best-practices confluence enterprise sdlc jira-software safe marketplace-apps

Praecipio Consulting is an Atlassian Platinum Partner

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

atlassian-platinum-solution-partner-enterprise

In need of professional assistance?

WE'VE GOT YOUR BACK

Contact Us