quarterly review 2

Performance Review Discussion

The performance review conversation revolves around the tracking of objectives, achievements, feedback, and the development of skills and experiences over time. This review is conducted section by section, with an emphasis on self-evaluation and identifying areas of focus for future improvement.

Overview of Objectives Tracking

  • The discussion begins with an acknowledgement of previous reviews and the importance of tracking against set objectives.
  • The invitee mentions noting down everything that wasn't achieved in the last review, emphasizing accountability for past objectives.
  • Key points discussed include:
    • Objectives Section: Outlined as a primary focus of the review.
    • Value Additions: Two points on value were mentioned alongside a list of testimonials to support claims of contributions and achievements.

Objective 1: AI Integration

  • The first objective set was embedding AI into the organization by September of the current year.
  • The target for increasing output by 4-5% is also noted.
  • The current status was reported as still at 0%:
    • Plans to improve Jira ticket output were discussed, targeting a tripling of output centered around enhancing delivery pace as confidence grows.
    • Emphasis was placed on understanding the AI delivery lifecycle, including pod-based delivery and advisory guidelines.
    • Active participation in IDLC (Intelligent Delivery Life Cycle) processes was encouraged as part of personal development.
Current Progress
  • Subtask Creation: A need for subtasks aligned with objectives is identified to enhance tracking and accountability. The invitee is encouraged to create these in the Yoda system:
    • Focus on understanding the AI delivery lifecycle through training and pods.
    • Direct references to participating in two bolts and aiming for consistent updates on contributions.
  • Current completion rates noted with specifics:
    • 100% participation in specified learning requirements, whereas Jira ticket output remains at a concerning zero.

Performance Metrics

  • Output Concerns: The challenge of measuring productivity using Jira ticketing is mentioned. Critiques arise regarding the effectiveness of generating tickets versus actual delivery quality:
    • Illustrative examples are given where one person generated seven tickets thought to be too many relative to actual output improvements.
    • An emphasis on balancing quantity (number of tickets) with the quality and effectiveness of work done.

Reflection and Adjustments

  • Discussion highlights balancing ongoing developments within objectives while achieving current targets. The reviewer's suggestions focus on:
    • Tailoring ticket outputs to reflect impactful work rather than sheer volume.
    • Calls for a deep dive during the next meeting to analyze ticket statistics and derive insights for future reviews.

Objective 2: Progress Check on Performance Development

  • Moving to other sections of the review about personal development, key areas covered:
    • Shadowing experienced engineers and effectively participating in project training.
    • The importance of the Personal Development Plan (PDP) is stressed as a tool for tracking ongoing progress and participation.
  • Self-reports on completion rates for set objectives are shared, with some areas like QA testing dialed down to 66% due to outstanding sessions.
    • Future Session Planning: Continued work with senior developers to enhance current skills was proposed, showing an understanding of pathways for personal development.

Conclusion on Career Path Framework

  • The conversation transitions to the career path framework, where:
    • A detailed checklist is recounted, mentioning approximately 32-33 targets, with discussions on achieving and partial completions noted.
  • Examples of significant contributions include:
    • Taking ownership of the Career Path Framework migration and enhancing long-term architecture projects.
    • Participation in CDLs and successfully debugging and resolving real-time application issues.
  • The importance of continuous improvement and the evolution of engineering practices is reiterated, using the framework as a backbone for skill reviews and accountability.

Documentation and Evidence Capture

  • Strategies for capturing documentation and evidence of achievements throughout the quarter were established.
    • Notable reports such as Git commits, meeting records, and stakeholder meeting transcripts are emphasized as integral parts of demonstrating progress.
    • Suggestions for improvement were made around including links to documentation in the performance reports for easier access and validation.

Performance Reviews and Values Framework

  • Continuous encouragement for the invitee to ask for regular feedback highlights a commitment to improving documentation and conscientious work habits:
    • Emphasis on community involvement and contributions, relevance to personal growth, and tracking behaviors through shared experiences were highlighted.
  • The closing remarks focus on next steps: verifying objectives and progress while also worrying about feedback loops and peer reviews to enhance skills and career trajectory.

Overall, the conversation encapsulates a thorough review of both performed and required objectives, with focused plans for improvement, evidence-based tracking, and an emphasis on continued growth and accountability within the work environment.