Project Managers (PMs)

Skills / Competencies

PMs’ Responsibilities Assessment Category:

Responsiveness & Commitment 5

• Adheres consistently to published work schedules for the department.

• Is consistently responsive during working hours on all official communication channels (Conferences, chats and or instant messaging) in a reasonable time and responds to emails in a timely manner.

• Respects and honors all agreed deadlines.

• Attends all meetings, even those scheduled with short notice during working hours.

• Always announces in advance to all stakeholders if it will not be possible to attend any job-related commitment, detailing the cause (illness, leave, etc.)

EVALUATION CRITERIA:

Needs strong improvement:

1. Does not give importance to the objectives, worries about his/her routine.

2. Frequently fails to comply with the work schedule.

3. Does not attend scheduled meetings.

4. Has a low level of commitment to the organization.

5. Does not deliver what promises to others.

Needs improvement:

1. Fails to meet the objectives assigned.

2. Fails to comply with working hours.

3. Arrives late to scheduled meetings.

4. Medium level of commitment to the organization.

Consistently meets expectations:

1. Commits to meeting the established objectives.

2. Sets goals higher than expected and meets them.

3. Studies and trains to improve performance and motivates others to do the same.

4. Complies with working hours.

5. Attends scheduled meetings in a timely manner.

Exceeds expectations:

1. Has a high level of commitment to meeting organizational objectives.

2. Has a high degree of responsibility for meeting the objectives of department and team.

5 IMPORTANT NOTE: Although the “Responsiveness & Commitment” Skill / Competency is part of the organizational Skills, it will be assessed after each sprint in the Software Development department.

3. Exceeds in meeting objectives and far exceeds job expectations.

4. Constantly looks for ways to optimize performance.

Superb:

1. Makes proposals to improve processes.

2. Overcomes difficulties in an extraordinary way.

3. Invests extra time to develop proposals that contribute to the achievement of objectives.

4. Anticipates possible inconveniences and avoids them.

Execution and follow-up of the sprint calendar

• Ensure all the sessions are executed as defined in the sprint calendar.

EVALUATION CRITERIA:

Needs strong improvement:

1. Most or all the sprint calendar sessions aren’t planned, scheduled or carried out correctly or within their time box or is needed to be reminded constantly (at least 3 times) to do so.

Needs improvement:

1. Some of the sprint calendar sessions aren’t planned, scheduled or carried out correctly or within their time box or is needed to be reminded often (at least 2 times) to do so.

Consistently meets expectations:

1. All the sprint calendar sessions are planned, scheduled or carried out correctly and within their time box and rarely (at least 1 time) needs to be reminded to do so.

Exceeds expectations:

1. All the sprint calendar sessions are planned, scheduled or carried out correctly and within their time box without any reminders.

Superb:

1. All the sprint calendar sessions are planned, scheduled or carried out correctly and within their time box. Sessions that require the Tech Lead or Product Owners are followed and monitored, meeting summaries are sent to attendees and attendance (tardiness and absences) is always tracked.

Backlog Review

• Coordinate with the Product Owner to ensure having complete stories in queue, ready for their attention.

EVALUATION CRITERIA:

Needs strong improvement:

1. There isn’t any tangible coordination with the Product Owner and the Development Team to maintain a healthy backlog.

Needs improvement:

1. There is some coordination with the Product Owner and the Development Team, but the backlog barely has enough work for a sprint or two or many stories are missing details, Definition of Done or Definition of Ready and are too big to be completed within a sprint. Consistently meets expectations:

1. Most of the time the Product Owner and the Development Team have backlog that contains at least 2 sprints worth of stories, but some are stories are missing descriptions, a verified Definition of Done or Definition of Ready or aren’t small enough to be completed within a sprint.

Exceeds expectations:

1. Ensures that the Product Owner and the Development Team most of the time have backlog contains at least 3 sprints of stories mayorly fully groomed, fully described and with a verified Definition of Done or Definition of Ready and are small enough to be completed within a sprint.

Superb:

1. Ensures that the Product Owner and the Development Team always have backlog contains 3 sprints worth of stories fully groomed, fully described and with a verified Definition of Done or Definition of Ready and are small enough to be completed within a sprint.

Distribution of workloads

• Ensure all team members always have tasks assigned to them.

EVALUATION CRITERIA:

Needs strong improvement:

1. There is no workload planning or team members spend entire days or have frequent long periods without work assigned or there are coworkers with a much higher load than others or Planning Poker is not being utilized.

Needs improvement:

1. There is some workload planning, but some team members have long periods without work assigned and there are coworkers with a higher load than others or Planning Poker is not being utilized effectively.

Consistently meets expectations:

1. The workload is mostly distributed. Planning Poker is utilized most of the time and is effective, and team members don’t have frequent periods without work assigned and there are few coworkers with a high workload.

Exceeds expectations:

1. Workload is properly distributed. Planning Poker is always used and is effective, and team members hardly have any periods without work assigned, there aren’t coworkers with a high workload.

Superb:

1. Workload is superbly distributed. Expectations and Results are set, Planning Poker is utilized effectively, Team members have a fair distribution of workload and once the sprint has been started there is little to no changes with the workload, the team is also mature enough to take on additional tasks if they finish early.

Follow up tasks

• Ensure compliance by following up all team members’ tasks during the sprint.

EVALUATION CRITERIA:

Needs strong improvement:

1. There is no follow-up of progress done, or it was done at the end of the sprint (when there isn’t time to react and correct deviations) or is needed to be reminded constantly (at least 3 times) to do so or the status of Stories and Tasks are not kept up to date.

Needs improvement:

1. Follow-up of progress is almost exclusively done through Jira, with little to no interaction with the Development Team or is needed to be reminded often (at least 2 times) to do so or of most Stories and Tasks are not kept up to date.

Consistently meets expectations:

1. Follow-up is made through Jira and sessions with the Development Team and the Tech Lead through the entire sprint and rarely (at least 1 time) needs to be reminded to do so and the status of most Stories and tasks are kept up to date.

Exceeds expectations:

1. Follow-up is made through Jira and sessions with the Development Team and the Tech Lead through the entire sprint and doesn’t need to be reminded to do so and the status of most Stories and tasks are kept up to date.

Superb:

2. Is always fully aware about the progress of the team and lets others know about progress (when relevant), utilizes Jira and does sessions with the Development Team and the Tech Lead through the entire sprint. Doesn’t need reminders about follow-ups and all Stories are tasks are always kept up to date.

Ticket documentation review - Evidence

• Ensure that tickets have the required documentation, such as Dev and QA tests, as well as information for release in production.

EVALUATION CRITERIA:

Needs strong improvement:

1. Most or all Stories and Tasks are missing documentation / supporting evidence / release information or is not clear or satisfactory or was updated exclusively at the end of sprint or is needed to be reminded constantly (at least 3 times) to do so.

Needs improvement:

1. Some Stories and Tasks are missing documentation / supporting evidence / release information, or the quality of the documentation or evidence is not clear or satisfactory or is needed to be reminded often (at least 2 times) to do so.

Consistently meets expectations:

2. Most tickets have clear documentation / supporting evidence / release information which was documented throughout the sprint and rarely (at least 1 time) needs to be reminded to do so.

Exceeds expectations:

1. Most tickets have clear documentation / supporting evidence / release information that is clear and satisfactory which was documented throughout the sprint and doesn’t need to be reminded to do so.

Superb:

1. All tickets have clear documentation / supporting evidence / release information that is clear and satisfactory which was documented throughout the sprint.