Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
stylenone

Overview

Audience: Subteam leads.

This document is intended to guide the selection process for a new Project Manager project manager and is to be used by directors and subteam leads. The candidate does not have to meet all the criteria points.

Criteria

General

...

:

  • Is a subteam member for at least 1 term

  • Actively participates in sub-team meetings and has completed subteam meetings

  • Completes assigned tasks reasonably on - time

  • Collaborates well with subteam members

  • Motivated to lead a project (or projects)

  • Collaborates well with the rest of the sub-team

Management Criteria

  • Communication: The project manager is able to convey the technical details

Category

Able to:

Technical: Understand the system, in detail and as a whole, to constribute to its improvement.

  • Contribute to defining project objectives, scope, and plans

  • Justify and challenge design decisions, tradeoffs, and limitations

  • Understand the expected behaviour of the project and

...

This includes task setting and Definition of Done (DOD)

...

Able to delegate tasks

Technical Criteria

...

Vision and goal

  • The project manager has a clear idea of what a finished project should be and do, in relation to the rest of the system(s)

The project manager has knowledge of:

...

Theoretical background of the project

...

How the components of the project work in general

...

How the components interface (with clear definitions and reasons for the abstraction)

...

How the project behaves with various input

...

Which parts of the project are unit testable, and why

...

What needs to be done to set up an integration test framework around the project

...

  • components

  • Understand how the project integrates with other projects

  • Triage issues and rapidly narrow down potential sources of error

  • Ensure maintainable and testable components

  • Maintain and update integration testing methods (e.g. SITL, HITL)

  • Maintain and update tooling

Vision: Direction, growth, and development of the team.

  • Provide clear direction and technical goals for a working system

Initiative: Proactive action.

  • Identify and mitigate technical risks

  • Create tasks with minimal interdependencies (i.e. decoupled)

  • Take ownership of technical challenges

  • Research and experiment with new tools and technologies

  • Revisit design decisions

Prioritization: Allocation of resources, due dates, and setting goals.

  • Estimate time and resource usage for tasks

  • Reevaluate and take corrective action for tasks that exceed time and resource estimates

  • Make decisions prudently with consideration to the impact of other projects and subteams

Collaboration: Communication, coordination, and leadership.

  • Lead by example and act as a role model

  • Involve members in decision making process

  • Provide constructive feedback and mentoring

  • Foster an positive and productive work environment

  • Resolve engineering disagreements: Resolving Engineering Disagreements

  • Maintain clear lines of communication and an active presence

  • Coordinate with other projects

Administration: Organization of procedures

  • Express ideas clearly and concisely in writing

  • Record design decisions and justification

  • Maintain technical documentation

  • Attend meetings, scheduling any additional if necessary