Category: PM Team Space

🔎 QA Scope

Supported browsers and devices:

🤝 Team

Description

Issue overview:

Scope of work:

References:

🔗 Accesses & Useful links

  Milestones

Weekly follow up and updating clients

Case: client doesn’t send us images we need to complete the task

1. If user doesn’r send information we need it is not client’s issue. It is our issue

2. Create a follow up task for yourselve to remind him at least once a week.

3. One time per week when you go through follow up tasks and send a friendly reminder to the customer that you need images, content, access to complete the task.

4. Also you can ask who can help you with your question from client’s team. So you will be able to contact responsible person and get required information quicker.

Metric: Velocity / Throughput

Goal: Predictability (=>90%), the upward trend over time for the velocity/throughput numbers.

Description:

Can be performed with the help of Jira report – compares commitment vs completed tasks or story points. Helps the Team decide how many tasks they may forecast for the current Sprint. Helps Product Owners to gauge how quickly a team may work through the backlog (predictability). In order to track velocity, teams need to be using a particular measure (story points, ideal days, etc.) Drawback: it’s not always accurate for future prognosis, depending on many unstable factors. 

Metric: Time to production (Cycle time) 

Goal: As short as possible, without sacrificing quality or business value.

Description:

Cycle time measures the time from “In Progress – to – Done”. By tracking and analyzing the Cycle Time, it is easy to identify bottlenecks in the process and decrease time to production.

Metric: Escaped Defects

Goal: 0 escaped defects

Description:

This metric track the number of issues/bugs that “escaped“ our testing cycle and were found by client/customers. This can be tracked on Jira by introducing and using a particular field in “Bug“ issue type. e.g Found by customer/Escaped Defect – Yes/No. Every “escaped defect“ should prompt improvements to our test cycles/environments/automated tests.

Metric: On-Time/On Budget/On Scope

Goal: Achieve/exceed expectations

Description: Each team should track their schedule, scope, and budget constraints, and take necessary actions in case of missing. Analyzing the issues with those needs to lead to a retrospective outcome of which need to be action points that would help us prevent such situations in the future.

Metric: Customer Satisfaction Score

Goal: 10 / highest score possible

Description:

We need to satisfy the needs of our customers, therefore the best way to measure our productivity is to ask our customers. This can be done on a regular basis, by asking our client to rate the team’s performance on a scale of 1-10, or in a form of an NPS score (how likely would you be to recommend CheITGroup?).

Change/Issue/Risk Management template is used to document changes, issues, and risks during the project. The documentation should be updated on the regular basis to outline the current state of things.

A request for proposal (RFP) is a document that solicits a proposal, often made through a bidding process, by an agency or company interested in procurement of a commodity, service, or valuable asset, to potential suppliers to submit business proposals.

https://docs.google.com/document/d/1pUgPG6g8Y-yBf7Z9NxVURksvSM-CLazhsiBVr_9ND8A/edit?usp=sharing

A statement of work template agreed upon between an agency and a client clearly defines what work to include within a project and what isn’t part of it. In itself, an SoW template is a project contract that establishes and aligns the expectations for both parties.