rfc 120 individual capacity planning in jira cloud

RFC 120: Individual Capacity Planning in Jira Cloud

By William Johnson
AD

Embarking on a journey to streamline your project management? RFC 120 Individual Capacity Planning, when harmonized with Jira Cloud, can significantly enhance your team's efficiency and output. Let's delve into this methodology and how to implement it on Jira's cloud-based platform.

RFC 120, a project management workflow proposed by Ron Jeffries, is centered around the idea of planning work on an individual level. When combined with Jira Cloud's robust features, this approach offers a structured way to manage tasks, track progress, and boost overall productivity.

Understanding RFC 120 in Jira Cloud

To kickstart, let's grasp the fundamentals of RFC 120 and its relevance in Jira Cloud. This methodology breaks down work into tasks, estimates the effort required, and encourages pulling tasks one by one.

AD
Caching JQL search in Jira Cloud
Caching JQL search in Jira Cloud
Jira Tutorial – Complete Guide to Project Management and Issue Tracking
Jira Tutorial – Complete Guide to Project Management and Issue Tracking
How To Do Resource Planning In Jira: Workaround & Tips
How To Do Resource Planning In Jira: Workaround & Tips

Jira Cloud, with its agile project management capabilities, provides the perfect playground for RFC 120. It allows you to create boards, manage sprints, and track work-items, all of which mirror RFC 120's core principles.

Setting Up Your Jira Board

Your Jira Cloud journey begins with setting up a board. This is where your team's tasks, or 'stories' in agile lingo, will reside. Customize your board's columns to reflect RFC 120's workflow stages: To Do, In Progress, Done.

Scaling Jira Cloud migrations with external importers
Scaling Jira Cloud migrations with external importers
How to Create Issue Templates for Jira?
How to Create Issue Templates for Jira?
Software Development Templates | Jira Template Library | Atlassian
Software Development Templates | Jira Template Library | Atlassian

Pro tip: Consider using swimlanes to represent individual team member's tasks. This adds a layer of transparency and reinforces RFC 120's individual focus.

Estimating Tasks with RFC 120

RFC 120 recommends estimating tasks in terms of ideal engineering days. In Jira, use story points to denote effort. Break down complex tasks into smaller, manageable chunks for more accurate estimation.

AD

Remember, RFC 120 encourages ongoing estimation refinement. Track velocity (the average number of story points completed per sprint) to continuously calibrate your estimates.

Jira Software roadmaps | Atlassian
Jira Software roadmaps | Atlassian
RCCP: Your Complete Capacity Planning Guide for 2026
RCCP: Your Complete Capacity Planning Guide for 2026
Capacity Planning
Capacity Planning
Capacity Requirements Planning (CRP) - 3 important tips
Capacity Requirements Planning (CRP) - 3 important tips
Master JIRA COURSE
Master JIRA COURSE
Introducing Jira Work Management - Inside Atlassian
Introducing Jira Work Management - Inside Atlassian

Implementing RFC 120's Pull System

RFC 120 emphasizes pulling work based on capacity. This ensures teams aren't overcommitting and encourages a sustainable pace.

In Jira Cloud, reflect this by limiting work in progress (WIP). Use Jira's built-in WIP limits or, for more control, consider using a third-party app like WIP Limits for Jira.

AD

Pulling Tasks in Jira

To adhere to RFC 120's pull principle, team members shouldn't grab more tasks than they can complete in a sprint. They should 'pull' tasks from the To Do column into their swimlane only when they have capacity.

a diagram showing the stages of progression in jlra, including testing and development
a diagram showing the stages of progression in jlra, including testing and development

And here's a trick: Use Jira's 'Estimated Time Remaining' field to keep a close eye on your team's capacity and workload balance.

Track and Adjust: The Continuing Cycle

RFC 120 isn't static; it's a cycle of planning, doing, reviewing, and adapting. In Jira, use reports and analytics to monitor team velocity, track lead times, and identify bottlenecks.

AD

Regularly review and adjust your capacity planning as needed. Remember, the goal is sustainable pace, not maximum output. Plan for regular improvement, not just for right now.

Integrating RFC 120 into Jira Cloud marks a significant step towards agile excellence. With a little fine-tuning, you'll witness improved productivity, less overwhelm, and happier teams. So, don't just manage tasks; empower your team to pull, build, and deliver great work. Your journey with RFC 120 and Jira Cloud awaits!

AD