Extreme Programming For Safire Solutions

1. Identify the actors of the given system:

 Resource Manager: Responsible for managing the competencies of the team

members, project details, and project roles.
 Business Analyst: Responsible for gathering project requirements and defining
competencies for business analysis roles.
 Technical Staff: Responsible for the technical aspects of the projects and
obtaining/renewing technical certifications.
 Project Manager: Responsible for project management and ensuring the project
team has the required competencies.

2. Identify the activities from the perspective of the roles:

Resource Manager:

 Add project details to the system.

 Add various project roles and their details.
 Add and modify details of project members, including certification status.
 Generate a status report for mismatching competencies.

Business Analyst:

 Define competencies and certifications for business analysis roles.

Technical Staff:

 Obtain/renew technical certifications.

 Update certification status in the system.

Project Manager:

 Oversee project management certifications and competencies.

 Ensure the project team meets the required competencies.
3. Design a tracker to design the tasks, subtasks if involved, and milestones:

| Expected Roles Needed |

Expected Years of
Role Experience Expected Certifications

Business Analyst 2 years Domain-specific certification

Technical certification (e.g., Java,

Technical Staff 3 years Python)

Project Manager 5 years PMP (Project Management Professional)

| Project Members Details |

Name Role Certification Status

John Doe Business Analyst In progress

Jane Smith Technical Staff Certified

Michael Johnson Project Manager Certified

| Milestones |

Milestone Task Subtask Assigned To Status

Requirement Gather project In

Gathering requirements - John Doe progress

Requirement Finalize scope and Not

Gathering deliverables - John Doe started

Development UI design, Implement In

Phase Develop frontend features Jane Smith progress

Development Database design, API Not

Phase Develop backend integration Jane Smith started
Milestone Task Subtask Assigned To Status

Conduct user Michael Not

Testing Phase acceptance testing - Johnson started

Not
Testing Phase Fix bugs and issues - Jane Smith started

In this tracker, each section represents different aspects of the project and its
management:

1. Project Details: This section captures basic information about the project, such
as its name, ID, client name, and the number of team members expected for the
project.

2. Expected Roles Needed: This section lists the various project roles (e.g.,
Business Analyst, Technical Staff, Project Manager) along with their expected
years of experience and required certifications.

3. Project Members Details: This section captures the details of project team
members, including their names, assigned roles, and certification status.

4. Milestones: This section tracks project milestones, tasks, subtasks, assigned

team members, and their completion status. This helps in tracking the progress
of the project.

In this example, we have one project named "Safire Portal" with Project ID "PRJ001" for
the client "ABC Company." The project is expected to have a team of 5 members.

The expected roles needed for the project are a Business Analyst with at least 2 years
of experience and a domain-specific certification, Technical Staff with at least 3 years of
experience and a technical certification, and a Project Manager with at least 5 years of
experience and a PMP certification.

In the project members details, we have John Doe as the Business Analyst currently in
progress with the certification, Jane Smith as the Technical Staff certified in the required
technology, and Michael Johnson as the Project Manager certified with PMP.

The milestones section captures the key milestones in the project, their associated
tasks, subtasks, the team member assigned to each task, and the current status of each
task.
4. Design user stories that indicate what each role in the system will do and
receive from the system and capture them in a user story document:

User stories for each role:

 As a Resource Manager, I want to add project details, project roles, and project
members with their certification status to the system for efficient competency
tracking.
 As a Business Analyst, I want to define competencies and certifications for
business analysis roles, ensuring the team meets industry standards.
 As a Technical Staff, I want to update my certification status in the system,
ensuring it is up-to-date for the assigned projects.
 As a Project Manager, I want to oversee project management certifications and
competencies, ensuring the team is equipped for successful project delivery.
 As a Resource Manager, I want to generate a status report for mismatching
competencies, identifying any gaps between required and obtained certifications.

5. What are the areas that need to be tested for bringing out an efficient system.
Design a test document:

Areas to test for an efficient system:

1. Project Details Entry:

 Test if the Resource Manager can successfully add project details to the system.

2. Project Roles and Details:

 Test if the Resource Manager can add various project roles and their details.
 Test if the Business Analyst can define competencies and certifications for roles.

3. Project Members Management:

 Test if the Resource Manager can add and modify project member details,
including certification status.

4. Certification Status Update:

 Test if the Technical Staff can update their certification status in the system.

5. Competency Report Generation:

  Test if the Resource Manager can generate a status report for mismatching
competencies.

6. Integration Testing:

 Test if the different components of the system are integrated and functioning
smoothly.

7. Usability Testing:

 Test the system's user-friendliness and ease of use for all roles.

8. Security Testing:

 Test the system's security measures to protect sensitive data.

9. Performance Testing:

 Test the system's performance under different loads to ensure smooth operation.

10. Compatibility Testing:

 Test the system on different devices and browsers to ensure cross-platform

compatibility.
 Design a test document with specific test cases, expected results, and actual
results for each of the above areas to ensure the efficient functioning of the
system.