Extreme Programming for Safire Solutions
1) Actors:
[Link] Manager
[Link] Owner
[Link] Lead
[Link]
[Link]
[Link] Lead
[Link] Engineer
[Link] Designer
2) Activities from the perspective of the roles:
[Link] MANAGER
Works on a higher level of abstraction and is responsible for a budget, risk,
schedule, and contract management.
[Link] 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 maximisation (suitability
of the product to use). Product owners are focused on constant changes because
they are using agile methodology.
[Link] 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.
[Link]
is a programmer having broad range of knowledge and skills over any technology
that related to the project.
[Link] 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.
[Link] 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.
[Link]:
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.
[Link] DESIGNER
The primary duty of the UI 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.
3) 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 [Link] 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 >>
Primary Sub Tasks No Of Total Schedule Schedule Milestone Iteration
Task Developer effort d Start d End Required
s hours
require
d (hrs)
Project << total << total << << end << Total – 3
Automatio developer effort Primary date of Milestones Iterations
n s from all hours task start the final to be
sub includin date>> sub task completed>
tasks>> g all >> >
sub
tasks>>
Adding 1 24 17-Feb- 19-Feb- Approval To be
Project 2022 2022 from complete
Details Resource d in
Functionali Manager Iteration
ty 1
Testing 1 16 20-Feb- 21-Feb- Unit test To be
Adding 2022 2022 sign off complete
Project d in
Details Iteration
functionalit 1
y
<< Add << Add
other other sub
primary tasks>>
tasks>>
4) 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 >>
5) 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]
6) Designing a Test Document
[Use the given Test Document temaplate]
