Scribd
Upload
17 views

Extreme Programming

Extreme Programming for Safire Solutions outlines roles for project teams using agile methodology including: Project Manager, Product Owner, Team Lead, Developer, Tester, QA Lead, QA Engineer, and UI Designer. It provides details on primary tasks and subtasks for each role, and templates for task tracking sheets, user stories, requirement analysis, and test documentation to plan and manage the agile project lifecycle.

Uploaded by

nikita dubey
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
17 views

Extreme Programming

Extreme Programming for Safire Solutions outlines roles for project teams using agile methodology including: Project Manager, Product Owner, Team Lead, Developer, Tester, QA Lead, QA Engineer, and UI Designer. It provides details on primary tasks and subtasks for each role, and templates for task tracking sheets, user stories, requirement analysis, and test documentation to plan and manage the agile project lifecycle.

Uploaded by

nikita dubey
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Extreme Programming for Safire Solutions

Actors:

1. Project Manager
2. Product Owner
3. Team Lead
4. Developer
5. Tester
6. QA Lead
7. QA Engineer
8. UI Designer

Activities:

1. PROJECT MANAGER: Works on a higher level of abstraction and is


responsible for a budget, risk, schedule, and contract management.
2. PRODUCT OWNER: is a person is close to that of an analyst and
concentrates on a product and its features. Their primary role is to take
care of business value maximization (suitability of the product to use).
Product owners are focused on constant changes because they are using
agile methodology.
3. TEAM LEAD: Typically, such a role is given to one of the developers.
This person should have leadership qualities which allow for maintaining
communication between remote development teams and for example -
clients. Team leads ensure that the team has sufficient performance levels
and is also responsible for conflict prevention and resolution.
4. DEVELOPER: is a programmer having broad range of knowledge and
skills over any technology that related to the project.
5. QA LEAD: Quality Assurance Lead is responsible for building the QA
team and its management. One of their most crucial responsibilities is to
ensure a proper relationship level between persons accountable for areas
of the system under construction. QA Lead, similarly, to a Team Lead, is
a person accountable for proper relations between QA team members,
mitigation of conflicts, praising good work, and motivating to further
self-development.
6. QA ENGINEER: It's a person responsible for preparing tools that allow
for automating processes which verify software quality. Such a form of
software testing makes it possible to check if regression errors occur.
7. TESTER: They are responsible mainly for conducting manual tests, that
is system verification by using it analogically, as opposed to how end
users will operate it.
8. UI DESIGNER: The primary duty of the Ul designer is to prepare, or
design, the user interface. This means transferring content, style, graphics
connected with a client or product to a system presentation layer.

Primary Sub Tasks No Of Total Scheduled Scheduled Milestone Iteration


Task Developers effort Start End Required
hours
required
(hrs)
Project << total << total << << end << Total – 3
Automatio developers effort Primary date of Milestones Iterations
from all hours task start the final to be
sub including date>> sub task completed>>
tasks>> all sub >>
tasks>>

Adding 1 24 17-Feb- 19-Feb- Approval To be


Project 2022 2022 from complete
Details Resource in
Functionality Manager Iteration 1

Testing 1 16 20-Feb- 21-Feb- Unit test sign To be


Adding 2022 2022 off complete
Project in
Details Iteration 1
functionality
< Add << Add
ther other sub
rimary tasks>>
asks>>
1) Design a tracker to design the tasks, subtasks if involved and
milestones
<< For each activity identified above create a task sheet as shown
below , You are free to analyze and assume no.of developers,
Estimated Duration for that activity, Total effort hrs, scheduled start
and end time and various milestones>>

<< Iterations indicated in which iteration the functionality must be


completed and given to the customer >>

2) Design user stories that indicate what each roles in the system
will do and receive from the system.

[sample]
As a Resource Manager, I want to add Project Details to the system
so that I can manage the project at a higher level as well as further
more information will be added by other stakeholders of the system.

<< List down the other user stories from the perspective of the actor,
In this case the actor is the Resource Manager >>

3) An Agile based requirement analysis sheet


(Epic, User Story Role, User Story Name, Story Details, Acceptance
Criteria, Tasks, Team -> Analyst/Prep work, Development Estimate,
QA, Total User Story Hours)

[Use the Requirement Sheet template]

4) Designing a Test Document

[Use the given Test Document temaplate]

You might also like