![]() These functions commonly find the work they do falls into similar patterns and that work needs similar structures and processes in place, so this organizational model can streamline setting up workflows. ![]() When organizing by the team is too granular, or the work being done by teams changes quite frequently as is the case with many fast-moving companies today, some teams opt to organize around higher-level business units – for example Development, Product, Customer Success, etc. However, for businesses that tend to face more organizational changes, structuring Jira cloud projects by team or business unit quickly becomes a burden as project settings, permissions, members, and even workflows must be reconfigured. For organizations where teams are relatively self-sufficient and work is mostly insular in nature, this model is an obvious choice in that it is logical, easy to establish, and does not require cross-functional workflows. Team-based project organization is one of the most common methods for structuring Jira instances. There’s no right or wrong way for organizing cloud projects in Jira, but here are some of the best Jira workflow practices: Organize Projects by Team Therefore, when thinking about how to organize projects, it’s helpful to structure around which people (or groups of people) will be involved in moving issues through the system, who should have access to projects or see certain types of issues, which types of issues make sense to view and manage together through the workflow, and which issues should be treated similarly from a configuration and versioning perspective. Workflows of issues are also tied to projects. In Jira, projects are simply a logical grouping of issues, which, by being defined together, will share common configurations, permissions, versioning, etc. Many will default to team-based projects, which while perfectly viable and arguably the most common method for organizing Jira does not suit the needs of every team. It sounds basic enough, but too often engineering organizations don’t put enough thought into how projects are organized in Jira. Organize your projects in a way that’s actually relevant to your business While these options are not exhaustive, they are the ways we’ve seen engineering organizations have the most success. In Part 1 of this series, we’ll dig into the best practices we see when it comes to organizing projects within Jira. ![]() Guide your team to adopt these best practices and you’ll be able to significantly improve visibility and reporting, and take steps to optimize your organization’s engineering operations. In this blog series, we’ll be revealing some best practices that teams use to organize their work and optimize their workflows in Jira. It can be hard to know where to start in organizing Jira to work well for your organization. And while Jira can be a powerful system, it can be complex and confusing for managing and improving engineering operations. For many software development organizations, the primary tool for tracking the progress of ongoing projects and moving them through the workflow is Jira. We always think that the best place to start is with visibility into your team’s process and workflows. Engineering leaders we have the privilege of working with are constantly looking to improve on the operations of their team, create efficiencies, and set their teams up for success. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |