Skip to main content

2021-03-11 Meeting - Developer Time Allocation

Date

Attendees



Agenda/Notes

  • Before we begin, let's talk scope.  What's in and out for this meeting.
  • Just a wee bit of history, vision, and concurrent efforts (for context)
  • As-Is process discussion
    • ITSD comes in (focusing on custom apps)
    • BA gathers more info from the customer, makes std/non-std determination
      • Determines if this goes down the project or request path based on rough LOE
    • Creates remediation ticket (for service requests; projects go another route)
      • BA adds requirements and more info
      • BA Intake status
      • Change to Backlog status when ready for developer weekly grooming meeting to review
    • In weekly meeting (BAs and Devs)
    • Story point added (to measure complexity)
  • Bi-weekly planning meetings (BAs and Devs)
    • The ticket gets assigned to a specific developer 
    • Budget free time for urgent/unplanned issues
  • Daily stand-ups (11am)
  • Retrospectives near the end of each sprint (BAs and Devs - no leads or supervisors)
  • To-Be process discussion
    • Requirement gathering and documentation improvements (under the current Project Management project)
      • All requirements are likely to be stored in Confluence consistently (to achieve repeatable processes)
      • Confluence will store a Requirements Repository
      • This will allow tracking requirements for projects and service requests consistently
  • Weekly meeting flow, attendees, etc.


How do we ensure developers are available to projects (specific developer, specific time window)?

How do project tasks integrate with the service request process?  Or is that a separate process?

How to divvy up a developer's time (vacations, projects, busy work, remediation tickets)?

40 hrs/week

90% available (10% busy work)

PMs do monthly project planning to determine who and how much time is needed (for work, meetings, etc) for the life cycle of the project

Work type/time prioritization

  1. Developer vacation time
  2. Incidents
  3. High priority projects
  4. Projects
  5. Service Requests


Resource allocation matrix (several months out) - Big Picture may be able to accommodate this (Liz is working on it)


Action items

  • @a userIntroduce Requirements Repository to Confluence Governance team (include Liz, Rudy, Andrea, AFShin)
  • @a userIntroduce Confluence calendars for time off recording
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.