Skip to main content

Project Task Assignments - February 2025

Overview

This document outlines active and graveyard tasks for the MultiDev implementation project. Active tasks are currently in progress, while graveyard tasks are deprioritized but assigned for future pickup when resources become available.

Team Assignments​

Active Tasks​

Shipping Tool Implementation

  • Priority: High
  • Due Date: 2/28/2025
  • Description: Complete end-to-end testing of shipping tool, document configuration issues. Focus on error appearing on every other click.

UOwn/Progressive Configuration

  • Priority: Medium
  • Due Date: 2/28/2025
  • Description: Work with contractor to outline process and update vendors with flow for production credentials.

Petty Cash Transaction Fix

  • Priority: Medium
  • Due Date: 2/28/2025
  • Description: Investigate and resolve error in petty cash transactions for supplier. Document solution for accounting team.

Graveyard Tasks​

Bank Rec End-to-End Testing

  • Priority: Low
  • Due Date: 3/15/2025
  • Description: Complete comprehensive testing with large batch of transactions once initial configuration is stable.

Implementation Guidelines​

Meeting Presentation

When presenting these assignments:

  1. Start with overview of task organization (5 min)
  2. Review active assignments by person (15 min)
  3. Explain graveyard task concept (5 min)
  4. Address questions and adjustments (5 min)

Task Management in Asana​

Setup Instructions
  1. Create sections for "Active" and "Graveyard" tasks
  2. Set due dates as specified
  3. Include full descriptions provided
  4. Add dependencies as task relationships
  5. Configure custom fields for priority levels

Graveyard Task Guidelines​

Important

Graveyard tasks should only be pulled when:

  • Team member has unexpected bandwidth
  • All dependencies are resolved
  • Task activation won't impact critical path items
  • Business priorities haven't changed

Weekly Review Process​

  1. Review active task progress
  2. Assess resource availability
  3. Evaluate graveyard task priorities
  4. Update dependencies and timelines
  5. Adjust assignments as needed

Critical Dependencies​

graph TD
    A[Base Data Conversion] --> B[CSS Batch Testing]
    A --> C[Product Attributes]
    D[Security Matrix] --> E[User Management]
    F[Payment Types] --> G[Returns Validation]

Success Metrics​

CategoryMetricTarget
Active TasksCompletion Rate90% by due date
Graveyard TasksActivation RateMax 1 per resource
DependenciesBlocking Time< 2 days
CommunicationStatus UpdatesWeekly