-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Echo engineering team lines of effort #7556
Comments
Second helpings sprint (31 Dec-13 Jan) priorities@joeyyang @rkreyhsig @tomas-nava, below are tickets related to this sprint's higher-level priorities. 1. Single appeal view
2. Collection of appeals views
3. Task Tree
4. Mail Pilot5. VLJ Support Staff (formerly co-located) Pilot6. Other Pilots |
Cherry Blosson sprint (25 Mar-7 Apr) engineering priorities1. Hearing schedule
2. Frontend Bugs 💻🐞👟
3. Backend Bugs 📟🐞👟 |
Appomattox sprint (8-21 Apr) engineering priorities@kevmo, below are tickets that you and I will be working on related to this sprint's higher-level priorities. 1. Hearings
2. VSO
3. Task platform
4. Performance
|
Primavera sprint (22 Apr-5 May) engineering priorities@kevmo @lomky, below are tickets that we will be working on related to this sprint's higher-level priorities. 1. Queue table view
2. Case details view
3. Task platform
4. Organization model
5. Performance
|
Victoire sprint (6-19 May) engineering priorities@kevmo @lomky @hschallhorn, below are tickets that we will be working on related to this sprint's higher-level priorities. 1. Queue table view
2. Case details view
3. Task platform
4. Organization model
5. Performance
|
Ridgway sprint (20 May - 2 June) engineering priorities@kevmo @lomky @hschallhorn, below are tickets that we will be working on related to this sprint. We will be using Zenhub to track progress on tickets. 1. Pagination
2. Data cleanup
3. Task platform
4. Increase Access to Queue
|
Omaha sprint (3-16 June) engineering priorities@kevmo @lomky @hschallhorn, below are tickets that we will be working on related to this sprint. We will be using Zenhub to track progress on tickets. This workload assumes that the Echo team will be able to dedicate 5 developer weeks of time this sprint. 1. Pagination
2. Board groups
3. Task platform
4. Data cleanup
|
Marianas sprint (17-30 June) engineering priorities@kevmo @lomky @hschallhorn, below are tickets that we will be working on related to this sprint. We will be using Zenhub to track progress on tickets. This workload assumes that the Echo team will be able to dedicate 7 developer weeks of time this sprint. 1. ⭐ Pagination
2. Board groups
3. Task platform
4. Data cleanup
|
Independence sprint (1-14 July) engineering priorities@kevmo @lomky @hschallhorn, below are tickets that we will be working on related to this sprint. We will be using Zenhub to track progress on tickets. 1. Pagination (#10470)
2. Organizations
3. Tasks
|
Rapinoe sprint (15-28 July) engineering priorities@kevmo @lomky @hschallhorn, below are tickets that we will be working on related to this sprint. We will be using Zenhub to track progress on tickets. 1. Pagination (#10470)
2. Organizations
3. Tasks
|
Husky sprint (29 July - 11 Aug) engineering priorities@kevmo @lomky @hschallhorn, below are tickets that we will be working on related to this sprint. We will be using Zenhub to track progress on tickets. 1. Pagination (#10470)
2. Tasks
3. Organizations
|
Roosevelt sprint (12-25 Aug) engineering priorities@kevmo @lomky @hschallhorn, below are tickets that we will be working on related to this sprint. We will be using Zenhub to track progress on tickets. 1. Pagination (epic #10470)
2. Odds and ends
3. Front-end
4. Task model
|
Tsavo sprint (26 Aug - 8 Sep) engineering priorities@kevmo @lomky @hschallhorn, below are tickets that we will be working on related to this sprint. We will be using Zenhub to track progress on tickets. 1. Pagination (epic #10470)
2. Task model
3. Odds and ends
|
Hines sprint (9 Sept - 22 Sept) engineering priorities@kevmo @lomky @lowellrex, below are tickets that we will be working on related to this sprint. We will be using Zenhub to track progress on tickets. 1. Pagination (epic #10470)
2. SCM: Administratively Acting on Behalf of Others
3. Inactive Users
4. Task model
5. Odds and ends
|
Little Rock sprint (Sept 23 - Oct 6) engineering priorities@kevmo @lomky @lowellrex @yoomlam, sprint priorities for this sprint! Pagination (epic #10470)
Queue table view
SCM: Administratively Acting on Behalf of Others
Inactive Users
Task model
Configurable queues (Epic #10032)
Section 508 Accessibility Audit (Epic #12095)
|
Cornwallis surrender sprint (Oct 7 - Oct 20) engineering priorities@hschallhorn @lomky @lowellrex @yoomlam, sprint priorities for this sprint! Pagination (epic #10470)
Queue table view
SCM: Administratively Acting on Behalf of Others⭐️ 1. ✅ Administratively acting on behalf of other users #11991 Inactive Users⭐️ 1. ✅ Create UI for marking users inactive #12212 Task model
Section 508 Accessibility Audit (Epic #12095)
Odds and Ends
|
Armistice Sprint sprint (Oct 21 - Oct 31) engineering priorities@hschallhorn @lomky @lowellrex @yoomlam, sprint priorities for this sprint! Reduced capacity due to Caseflow Offsite in week 1. Inactive Users⭐️ 1. ✅ Update the task reassign function #12365 SCM: Administratively Acting on Behalf of Others⭐️ 1. ✅ Extend the organizations_user with judge & attorney roles #12420 Bug Investigation
Configurable Queues
Odds and Ends
Stretch Goals (fallout from last sprint)Section 508 Accessibility Audit (Epic #12095)
|
Susan B. Anthony Sprint (Nov 4 - Nov 15) engineering priorities@hschallhorn @lomky @lowellrex @yoomlam @ajspotts @jimruggiero sprint priorities for this sprint! Special Case Movement
Automatic Case Distribution
Inactive Users
Stretch Goals & CarryoverTasks
Accessibility
Misc
|
Gettysburg Address Sprint (Nov 18 - Nov 29) engineering priorities@hschallhorn @lomky @lowellrex @yoomlam @ajspotts @jimruggiero sprint priorities for this sprint! Special Case Movement⭐️ 1. (KAT) Update Code using JudgeTeam Admin to Determine Judge / Attorney #12422 Accessibility⭐️ 1. (ALEC) Table sort functionality not accessible to keyboard-only or other AT users. Sort buttons should be included in the tab order and be operable by keyboard #12126 Eliminate GenericTasks
Tasks
Inactive Users⭐️ 1. (HUNTER) Add instructions to reassigned tasks of inactive users #12506 Tech Debt
Stretch Goals
|
Operation Crossbow Sprint (Dec 3 - 12) Engineering Priorities@hschallhorn @lomky @yoomlam @ajspotts @jimruggiero priorities for this sprint! Special Case Movement #11801
Tech Debt
Quality Review
Stretch GoalsBat Team Improvements
Accessibility
Tech Debt
Other
|
SCORE Satellite Sprint (Dec 16 - Jan 12)@yoomlam, @ajspotts, @kevmo, @lomky, @jimruggiero , and @hschallhorn, Here are the sprint priorities for this sprint! 🐬 indicates complete, approved, and waiting for merge after code freeze ends SCM: Acting on Behalf of Others #11801
Inactive Users #12523
Bat Team Needs
Jim Needs
Stretch GoalsBat Team Needs
Accessibility
Tech Debt
|
Transcontinental sprint (Jan 13 - 26) engineering priorities@yoomlam, @ajspotts, @kevmo, @lomky, @jimruggiero , and @hschallhorn, here are the priorities for this sprint! SCM: Acting on Behalf of Others #11801
Inactive Users #12523
Bat Team Needs
Stretch GoalsGrand Unified Queue #10032
Accessibility
Tasks
Tech Debt
Documentation |
Echo engineering team's objective is to enable all teams to track and act on appeals as they move through the board. To that end we have four major lines of effort:
The broader Caseflow team is tracking the roadmap and timelines on a shared mural and using a waffle board to track various tickets that need to be completed.
In July, the Echo team adopted a strategy of voting for determining the level-of-effort estimate for each ticket. A dedicated Github ticket details this initiative in more detail.
1. Single appeal view
This initiative encompasses all of the work that will be done on the case details page. It includes case timeline and the various case details refinements.
2. Collection of appeals views
This includes case search as well as the many different incarnations of the queue table views (judges, attorneys, colocated, generic, all cases view).
3. Task tree
This is somewhat of a catch-all for the plumbing needed to make the task model work: organizational membership, task actions improvements, and maturing/extension of the task model.
4. Pilots
Currently we are piloting the queue functionality with the co-located administrative support team, Board judges, VSOs, and the quality review team. Upcoming pilots include Mail, litigation support, FOIA, and AOD.
The text was updated successfully, but these errors were encountered: