UA 740 - Unio Phase II Workflow

Getting Started

This guide is specifically about UA 740 - Unio Phase II work. Before diving in, we recommend reading the Workflow System Overview first—it explains our overall system and shows how different initiatives work. You might also find it helpful to check the Unio Project Workflow to see how our main product workflow compares.

Overview

UA 740 is the reason Unio exists. We built their union management system as a single-tenant V1 application, and it worked so well that when we won a contract for another union, we decided to transform it into a multi-tenant cloud platform. That's Unio.

This workflow covers Phase II development—a major feature expansion we're building for UA 740 as we continue enhancing their version of the system. Eventually, UA 740 will migrate to our new multi-tenant Unio platform, but for now, we're adding these enhancements to their current version.

About Coordinated Breakdown

The workflow is similar to the main Unio workflow but with one key difference: we use the Coordinated Breakdown Model instead of Team Autonomy. Here's what that means:

The feature breakdown happens right here in the UA 740 - Unio Phase II Space. We do feature planning on the 🚀 Features Board, then we break down work on the 🌊 Pipeline Board before distributing child cards to team sprints for execution. Don't worry if this feels like a lot right now—we'll dive deeper into all these concepts as we walk through the workflow.

The UA 740 - Unio Phase II Space

This is where all UA 740 - Unio Phase II planning happens. We plan features, organize them, and break down work here. Once features are broken down into child cards, those cards flow to team spaces (Design, Frontend, Backend, Infrastructure, Operations) for actual execution.

Think of this space as the coordination hub—where we decide what needs to be built and how to distribute it to teams. The actual building happens in team sprints, but you always come back here to see the big picture of Phase II work.

Board Structure

Let's walk through the boards we use for UA 740 - Unio Phase II work and what each one does.

Modules Board

This tracks the major system capabilities and features. Modules are permanent—they represent areas of the system that stick around and evolve over time.

Each module lives in one of these lists:

• 📋 Not Started - We haven't begun building this yet
• ⚙️ In Progress - We're actively working on features in this area
• ✅ Complete - Delivered and deployed

Examples of our modules: Welding Tickets, Dispatch, Member Profile, Search, User Management, Dashboard, Working Lists, Payments, Document Management

🚀 Features Board

This is where individual features move through the planning process. Each feature gets a FT-### number (FT-001, FT-002, etc.) and moves through these stages:

• 📥 Backlog - Features identified but not yet started
• 💡 Vision - Writing the vision document
• 📝 Requirements - Writing the requirements document
• 📐 Spec - Writing the technical specification
• 🗓️ Plan - Writing the implementation plan
• 📤 Distributed - Feature trackers have been created and distributed to the 🌊 Pipeline Board

🌊 Pipeline Board

This board serves two purposes: it tracks feature progress AND acts as the sprint backlog. Feature trackers live here while their child cards get pulled into team sprints.

The three lists organize work differently:

• 📋 Needs Breakdown - Features that need breaking down into sprint work
• 👀 Tracking - Feature trackers tracking overall progress across sprints
• 🔜 Sprint Queue - Child cards ready to pull into team sprints (this is your backlog)

🚚 Shipped Board

Simple and straightforward—this is where completed trackers live after all their child cards are done. It gives us history for reporting and sprint reviews.

Complete Workflow

Now let's walk through how work actually flows from initial planning to deployed features.

Phase 1: Planning

This is where features get defined and planned. You're working on the 🚀 Features Board, moving cards through the planning stages as you flesh out what needs to be built.

🚀 Features Board flow: 📥 Backlog → 💡 Vision → 📝 Requirements → 📐 Spec → 🗓️ Plan → 📤 Distributed

Here's what you'll do:

1. Create a FT-### card on the 🚀 Features Board
2. Link it to the appropriate Module card (sets the parent relationship)
3. Write the vision, requirements, spec, and plan documents—moving the card through each stage as you complete them
4. At the "🗓️ Plan" stage: Create feature trackers and distribute them to the 🌊 Pipeline Board
5. Move the feature card to the 📤 Distributed list once the feature trackers are created and distributed to the 🌊 Pipeline Board

What you'll have at the end: Feature trackers on the 🌊 Pipeline Board, with the feature card in "📤 Distributed"

Example:

• FT-003 - Go Paperless Initiative created on Features board
• Links to "Paperless Communication" module
• Currently moving through 📥 Backlog → 💡 Vision
• Will create feature tracker and distribute to Pipeline when we reach the 🗓️ Plan stage

Phase 2: Team Breakdown

Once planning is complete and feature trackers are distributed, the work moves to the 🌊 Pipeline Board. This is where the coordinator (or PM) breaks down features into concrete sprint work for teams.

Understanding the Pipeline Board:

Remember, this board serves two purposes: tracking feature progress AND acting as your sprint backlog (the 🔜 Sprint Queue).

The three lists work together:

1. 📋 Needs Breakdown - Features needing breakdown into sprint work
2. 👀 Tracking - Feature trackers tracking overall progress
3. 🔜 Sprint Queue - Child cards ready for team sprints (your backlog)

Notice how feature trackers use the first two lists (for tracking) while child cards use the third list (as the backlog).

How breakdown works:

1. Feature tracker arrives at 🌊 Pipeline Board in 📋 Needs Breakdown
2. The coordinator breaks it down into child cards for specific team work
3. Move the child cards to 🔜 Sprint Queue
4. Move the feature tracker to 👀 Tracking
5. Child cards get pulled into team sprints (Design, Frontend, Backend) as capacity allows
6. When all child cards complete, move the feature tracker to the 🚚 Shipped Board

Important note: Work flows into the same team sprint boards used for Unio work. Team members see all their work (Unio + UA 740) in one sprint, which keeps things simple and focused.

Phase 3: Sprint Execution

Now we're into actual delivery. Child cards from the Phase II Pipeline's Sprint Queue get pulled into team sprints every two weeks.

Team members work from their regular sprints—they'll see UA 740 cards right alongside Unio cards. This unified view means you only need to look at one place for all your work, regardless of which project it's for.

The sprint mechanics work exactly like the main workflow: cards move through To Do → Doing → Blocked → In Review → Done → Cancelled.

Phase 4: Deployment & Shipped Tracking

The final step is getting work into production and tracking what's been delivered.

When all child cards complete:

1. Deploy the feature to UA 740 production
2. Move the feature tracker from the 🌊 Pipeline Board to the 🚚 Shipped Board
3. Update the Module card if needed (for example, move it to "Complete" if this was the last feature for that module)

The 🚚 Shipped Board gives you history for sprint reviews and reporting—you can see everything that's been delivered over time.

Non-Phase II Work for UA 740

This space is specifically for UA 740 - Unio Phase II work. We also do other work for UA 740 that's not related to Phase II. That work doesn't belong here.

Instead, any UA 740 work that's not related to Phase II is handled through our Legacy Workflow. See the Legacy Workflow guide for how we manage that type of work.

Now You're Ready!

You've got the full picture: how to plan Phase II features, break them down in the pipeline, and move them through team sprints to deployment. You know where work lives, who sees what, and how everything flows together.

Time to dive in. Start planning your first feature, create a task tracker for something quick, or pull work into your next sprint. Phase II is ready for you.