ĐỀ 2 AGILE SCRUM

Request 1
Scrum Master: Internal stakeholder - The Scrum Master is an expert at leading teams using an Agile project
management approach. The Scrum Master facilitates all communication and collaboration between management and
team members to ensure that the results and targets are achieved.

- BA: Internal stakeholder - is a "bridge" to help connect customers with businesses. They exchange and receive
customer comments, then transmit these information to the internal team to find ways to develop project.

Developer team: Internal stakeholder - Responsible for product development. They will write, execute the code,
debug the software application.

Tester team : Internal stakeholder - Responsible for software testing. Perform bug finding, report bugs to the
software developer team.

Customer – External stakeholder - Provide requirement, user story to the team so that they build a project. They also
check each sprint result.

Request 2 : User stories in product backlog

As a *role* , i want to ... so that...
As a team member , I want to log-in through/via my email account in order to safe time while
logging in with no need to fill in the password
As a team member ,
Request 3 - Project Management System – level 1
1. Project Initiation – level 2
1.1 Define project scope and objectives – level 3
1.2 Identify stakeholders and their requirements– level 3
1.3 Create project charter– level 3
- Define project scope and objectives – level 4
1.4 Define project team roles and responsibilities– level 3
1.5 Conduct project kickoff meeting– level 3
2. Sprint 0: Planning and Setup– level 2
2.2 Create product backlog and prioritize features– level 3
2.3 Define sprint cycles and timelines– level 3
2.4 Set up development environment and tools– level 3
2.5 Define Definition of Done (DoD) – level 3
2.6 Develop release plan– level 3
3. Sprint 1– level 2
3.1 Sprint planning meeting– level 3
3.2 Develop user stories for sprint – level 3
3.3 Define sprint backlog and tasks– level 3
3.4 Develop software architecture and design– level 3
3.5 Implement core functionalities of DTS– level 3
3.6 Conduct daily scrum meetings– level 3
3.7 Test and validate sprint deliverables– level 3
3.8 Conduct sprint review and retrospective– level 3
4. Sprint 2– level 2
4.1 Sprint planning meeting– level 3
4.2 Develop user stories for sprint– level 3
4.3 Define sprint backlog and tasks– level 3
4.4 Implement additional functionalities of DTS– level 3
4.5 Conduct daily scrum meetings– level 3
4.6 Test and validate sprint deliverables– level 3
4.7 Conduct sprint review and retrospective– level 3
5. Sprint 3– level 2
5.1 Sprint planning meeting– level 3
5.2 Develop user stories for sprint– level 3
5.3 Define sprint backlog and tasks– level 3
5.4 Implement remaining functionalities of DTS– level 3
5.5 Conduct daily scrum meetings– level 3
5.6 Test and validate sprint deliverables– level 3
5.7 Conduct sprint review and retrospective– level 3
6. Sprint 4: Release and Deployment– level 2
6.1 Conduct final sprint planning meeting– level 3
6.2 Test and validate final release– level 3
6.3 Conduct final sprint review and retrospective– level 3
 6.4 Deploy DTS to production environment– level 3
6.5 Conduct post-release testing and monitoring– level 3
6.6 Close out project– level 3
Request 4

B–3 C–2
A–4
G–6

Start 0
E–4 F–2 End

D–5

H– 5
I–9

path 1 : Start A -> B -> C-> G-> End 4+3+2+6 = 15weeks

path 2 : Start D -> B -> C-> G-> End 5+3+2+6 = 16weeks
path 3 : Start D -> E -> F-> G-> End 5+4+2+6 = 17weeks
path 4 : Start D -> H -> I -> End 5+5+9 = 19weeks => critical path , 19weeks are the minimum duration
to complete that deliverable
Explain: To reduce the overall project schedule by 3 weeks, we will focus on reducing the amount in the
critical path. But after being reduced to 16 weeks , there is 1 more path that is exceeding this number
which is path 3 – 17 weeks. On the other hand, path 3 and critical path both have task D . Obviously , we
will have something to do with task D under crashing method
Crashing: In this method , we can try to shorten the duration of some of the critical path activities by
adding additional resources or working overtime.
Solution1 : we can add more workers to task D to complete it earlier than 3 weeks
Solution 2: we can force the team to work overtime in task D so that it can be completed earlier than 3
weeks.
Solution 3 : reward the team if they can complete task D earlier than 3 weeks

� Crashing will increase cost .

Request 5
The PMS project is targeted to going live officially after 7 months
 � DAC 7 months
PV after 5 months – 5000 -> BAC 7000
AC 6500
EV 7000 x 80% = 5600
CV = 5600 – 6500 = -900 <0 -> over budget
SV = 5600 – 5000 = 600 >0 -> above schedule
CPI = 0.86
SPI = 1.12
EAC = 7000/0.86 =8139
EDAC = 7/1.12 =6.25 months

TH2
BAC ( Budget at completion) – 5000$
DAC – 7 months
After 5 months
AC ( actual cost ) - 6500$
PV ( Planned value ) = 5000/7 x 5= 3571$
EV (earned value) = 5000 x 80% = 4000$
CV ( cost variance) = EV – AC = 4000-6500 = -2500 < 0 => over budget
SV ( schedule variance) = EV – PV = 4000 – 3571 = 429 >0 => ahead of schedule
CPI ( cost performance index ) = EV/AC = 0,6 < 1 => over budget
SPI ( schedule performance index ) = EV /PV = 4000/3571 = 1,12 >1 => ahead of schedule
EAC ( estimate at completion ) = BAC/CPI = 5000/0,6 = 8333 $
EDAC ( estimate duration at completion ) = DAC/SPI = 7 / 1,12 = 6,25 months
So this project is ahead of schedule but over budget
Behind schedule -> apply fast tracking method, crashing method , reduce the project scope
Over budget -> cut down on human resource , reduce the project scope
On schedule
On budget
Ahead of schedule
Under budget

DE 1 ITERATIVE INCREMENTAL
Request 1 – ĐỀ 1
Project manager: Internal stakeholder, planning and organizing, managing tasks, budgeting, controlling costs and
other factors. Everything they do helps make sure the project can be completed on time and on budget, and more
importantly, profitable.

BA: bridges the gap between external stakeholders and the development team, interpreting business requirements
into understandable development tasks to match a final software product with the expected business value

Developer team : internal stakeholder , He writes, debugs and executes the source code of a software application.

Designer team : internal stakeholder A UI/UX designer’s job is to create user-friendly interfaces that enable users to
understand how to use complex technical products

Tester team : Internal stakeholder. The role of a tester is to test out products for bug and provide reports to the
project teams about any issues or improvements that the product may require

Customer;.. external stakeholder plays a vital role in providing requirements, feedback, and validation during the
product development or service delivery process. Their satisfaction and adoption of the product/service are crucial
for business success and growth.

2 Request 2 Project scope statement

Project in-scope item :

● Our team will develop an website Project management system PMS to support project managers, team
members and other project stakeholders on following management area scope, cost , quality,
communication, schedule, issue
● This website will have 4 main releases which respectively provide the system functionalities for 4 roles:
system admin, team member, customer , project manager . 4 main releases will include about 30 usecase

Project deliverables :

● project schedule

● project charter

● project management plan (scope, time, quality, resource, communication, risks, stakeholder, procurement )

● test plan,

● code package for module 1-2-3,

● meeting minutes,

● project final report

Out of scope item :

● This project will not include payment to external vendors

REQUEST 3
Request 3:
1. Software Project Management System
1.1 Phase 1: Initiating (level 1)
1.1.1 Create Project Charter (level 2)
1.1.1.1 Solidifying the project scope (level 3)
1.1.1.2 Determine resources needed (level 3) Crashing -
1.1.1.3Define project SMART goal and deliverables (level 3 )
1.1.2 Hold a kick-off meeting (level 2)
1.1.3 Get project charter approval (level 2)
1.1.4 Perform a cost - benefit analysis for the project- - level 2
1.1.5 Create stakeholder Register (level 2)
1.2 Phase 2: Planning (level 1)
1.2.1 Create Project management plan ( level 2 )
1.2.1.1 Create Scope Management Plan (level 3)
1.2.1.2 Create Time Management Plan (level 3)
1.2.1.3 Create Cost Management Plan (level 3)
1.2.1.4 Create Risk Management Plan (level 3)
1.2.1.5 Create Resource Management Plan (level 3)
1.2.2 Meeting with team to discuss about plans (level 2)
1.2.3 Deliver Project Management Plan (level 2)

1.3 Phase 3 Executing (level 1) (Analysis , Design, Code , Test )

Iteration 1 – Level 2
1.3.1 Analysis (level 3)
1.3.1.1 Create Feasibility Report (level 4)
1.3.1.2 Create Use-case diagram and use-case description (level 4)
1.3.1.3 Create Software Requirement Specification (level 4)
1.3.1.4 Perform Requirement validation (level 4)
1.3.1.5 Perform Requirement management (level 4)
1.3.2 Design (level 3)
1.3.2.1 Create Architecture design (level 4 )
 1.3.2.2 Create detail design (level 4 )
1.3.3 Implementing (level 3)
1.3.3.1 Implement coding for module 1 : User management (level 4) (usecase 1
to 10 )

1.3.4 Testing (level 3)

1.3.4.1 Perform unit testing (level 4)
1.3.4.2 Perform integration testing (level 4)
Iteration 2 – level 2
1.2.1 Analysis (level 3)
1.2.1.1 Update Feasibility Report (level 4)
1.2.1.2 Update Use-case diagram and use-case description (level 4)
1.2.1.3 Update Software Requirement Specification (level 4)
1.2.2 Design (level 3)
1.2.2.1 Update Architecture design (level 4 )
1.2.2.2 Update detail design (level 4 )
1.2.3 Implementing (level 3)
1.2.3.1 Update coding for module 1 : (level 4)
1.2.3.2 Implement coding for module 2 : (level 4)
1.2.3.3 Implement coding for module 3 : (level 4)
1.2.4 Testing (level 3)
1.2.4.1 Perform unit testing (level 4)
1.2.4.2 Perform integration testing (level 4)
1.2.4.3 Perform part of system testing (level 4)
Iteration 3 – level 2
1.2.1 Analysis (level 3)
1.2.1.1 Update Feasibility Report (level 4)
1.2.1.2 Update Use-case diagram and use-case description (level 4)
1.2.1.3 Update Software Requirement Specification (level 4)
1.2.2 Design (level 3)
 1.2.2.1 Update Architecture design (level 4 )
1.2.2.2 Update detail design (level 4 )
1.2.3 Implementing (level 3)
1.2.3.1 Update coding for module 123 : (level 4)
1.2.3.2 Implement coding for module 4 : (level 4)
1.2.4 Testing (level 3)
1.2.4.1 Perform unit testing (level 4)
1.2.4.2 Perform integration testing (level 4)
1.2.4.3 Perform system testing (level 4)
1.2.4.4 Perform acceptance testing
1.3 Phase 4: Monitoring and Controlling (level 1)
1.3.1 Control scope (level 2)
1.3.2 Track progress (level 2)
1.3.3 Perform Cost control (level 2)
1.3.4 Monitor and control Risk (level 2)
1.4 Phase 5: Closing (level 1)
1.5.1 Create Lesson learn (level 2)
1.5.2 Create Project Final Report (level 2)
1.5.3 Create Project Archive (level 2)
1.5.4 Hold close Project Ceremony (level 2)

Request 4

C–2 F–3
I–3

Start 0 A–3 B–5 D–3 G– 5 End 0

E–5 H–4
- Nếu đề bắt define ES, EF, LS, LF, Float

ES Duration EF

< Activity>

path 1 : Start A -> B -> C-> F->I-> End = 16weeks

path 2 : Start A -> B -> D-> G->I-> End = 19weeks
path 3 : Start A -> B -> D-> H-> End = 15weeks
path 4 : Start A-> B -> E->H -> End = 17weeks

Path 2 is critical path , 19weeks are the minimum duration to complete that deliverable
Explain: To reduce the overall project schedule by 3 weeks, we will focus on reducing the amount in the
critical path. But after being reduced to 16 weeks , there is 1 more path that is exceeding this number
which is path 4 – 17 weeks. On the other hand, path 4 and critical path both have task B – 5 days which
can be reduced . Obviously , we will have something to do with task D under crashing method
Crashing: In this method , we can try to shorten the duration of some of the critical path activities by
adding additional resources or working overtime.
Solution1 : we can add more workers to task B to complete it earlier than 3 weeks
Solution 2: we can force the team to work overtime in task B so that it can be completed earlier than 3
weeks.
Solution 3 : reward the team if they can complete task B earlier than 3 weeks

� Crashing will increase cost .

BÀI 5 đề 1

PV – 5000
EV – 3000
AC – 4000
CV = EV – AC = -1000 > vượt chi phí
SV = EV – PV = -2000> chậm tiến độ
� , reduce the project scope

WATERFALL
cách 1 – waterfall truyền thống
1. Software Project Defect tracking system (level 1)
1.1 Phase 1: Initiating (level 2)
1.1.1 Create Project Charter (level 3)
1.1.1.1 Solidifying the project scope (in-scope item, out of scope item , deliverable ( level 4 )/ Write
down the project scope statement
1.1.1.2 Determine resources needed (level 4 )
1.1.1.3Define project SMART goal and deliverables (level 4 )
1.1.2 Hold a kick-off meeting (level 3)
1.1.3 Get project charter approval (level 3)
1.1.4 Perform a cost - benefit analysis for the project- - level 3
1.1.5 Create stakeholder Register (level 3)
1.2 Phase 2: Planning (level 2)
1.2.1 Create Project management plan ( level 3 )
1.2.1.1 Create Scope Management Plan (level 4)
1.2.1.2 Create Time Management Plan (level 4)
1.2.1.3 Create Cost Management Plan (level 4)
1.2.1.4 Create Risk Management Plan (level 4)
1.2.1.5 Create Resource Management Plan (level 3)
1.2.2 Meeting with team to discuss about plans (level 3)
1.2.3 Deliver Project Management Plan (level 3)

1.3 Phase 3 Executing (level 2) (Analysis , Design, Code , Test )

1.3.1 Analysis (level 3)
1.3.1.1 Create Feasibility Report (level 4)
1.3.1.2 Create Use-case diagram and use-case description (level 4)
1.3.1.3 Create Software Requirement Specification (level 4)
1.3.1.4 Perform Requirement validation (level 4)
1.3.1.5 Perform Requirement management (level 4)
1.3.2 Design (level 3)
1.3.2.1 Create High level design / Create Architecture design (level 4)
1.3.2.2 Create Low level design / Create detail design (level 4)
1.3.3 Prototyping (level 3)
1.3.3.1 Create prototype for module 1 (level 4)
1.3.3.2 Review prototype for module 1 with customer (level 4)
1.3.3.3 Create prototype for module 2 (level 4)
1.3.3.4 Review prototype for module 2 with customer (level 4)
1.3.3.5 Create prototype for module 3 (level 4)
1.3.3.6 Review prototype for module 3 with customer (level 4)
1.3.4 Implementing (level 3)
1.3.4.1 Implement coding for module 1 : User management (level 4)
1.3.4.2 Implement coding for module 2 : Requirement management (level 4)
1.3.4.3 Implement coding for module 3 : Defect tracking and reporting (level 4)
1.3.5 Testing (level 3)
1.3.5.1 Perform unit testing (level 4)
1.3.5.2 Perform integration testing (level 4)
1.3.5.3 Perform system testing (level 4)
1.3.5.4 Perform acceptance testing (level 4)
1.3.6 Support (level 3)
1.3.6.1 Training (level 4)
1.3.6.2 Documentation (level 4)
1.3.6.3 User support (level 4)
1.3.6.4 Enhancements (level 4)
1.4 Phase 4: Monitoring and Controlling (level 2)
1.4.1 Control scope (level 3)
1.4.2 Track progress (level 3)
1.4.3 Perform Cost control (level 3)
1.4.4 Monitor and control Risk (level 3)
1.5 Phase 5: Closing (level 2)
1.5.1 Create Lesson learn (level 3)
1.5.2 Create Project Final Report (level 3)
1.5.3 Create Project Archive (level 3)
1.5.4 Hold close Project Ceremony (level 3)
CV= EV - AC
SV = EV - PV
CPI = EV/AC
SPI = EV/PV
EAC = BAC/CPI
EDAC = DAC/SPI
ETC = EAC - AC

Bảng tóm tắt tính toán giá trị thu được EVM - Earned Value Management

PHÂN TÍCH GIÁ TRỊ THU ĐƯỢC

Viết Tên Định nghĩa Cách sử dụng Công thức Giải

tắt thích kết
quả

PV Giá trị kế Ngân sách Giá trị của công

hoạch được cấp cho việc kế hoạch được
Plan công việc hoàn thành tới một
value theo kế thời điểm, thường
hoạch là ngày dữ liệu,
hoặc hoàn thành dự
án.

EV Giá trị thu Phần công Giá trị kế hoặc của EV = tổng giá
được việc thực tất cả công việc trị kế hoạch
Earn hiện được đo được hoàn thành của công việc
value lường bằng (thu được) tại một đã hoàn thành
ngân sách đã thời điểm, thường
bỏ ra cho là ngày dữ liệu,
công việc đó. không nhắc đến chi
phí thực tế
AC Chi phí Chi phí phát Chi phí thực tế của
thực tế sinh khi thực tất cả công việc
Actu hiện công được hoàn thành tới
al việc của một một thời điểm,
cost hoạt động thường là ngày dữ
trong một liệu
khoảng thời
gian cụ thể.

BAC Ngân sách Tổng của tất Giá trị của tổng
khi hoàn cả ngân sách công việc kế hoạch,
Budg thành được thiết lập chi phí cơ sở dự án
et at để thực hiện
comp công việc.
letio
n

DAC Duration at
completion

CV Chênh lệch Số tiền ngân Chênh lệch giữa giá CV = EV - Dương =

chi phí sách thâm trị công việc hoàn AC Dưới chi
Cost hụt hoặc thành tới một thời phí
varia thặng dư tại điểm, thường là
nce một thời ngày dữ liệu, và chi Trung
điểm nhất phí thực tế tới thời bình =
định, thể hiện điểm đó. Đúng chi
bằng chênh phí kế
lệch giữa giá hoạch
trị thu được
và chi phí Âm =
thực tế. Vượt chi
phí kế
hoạch

SV Chênh lệch Thời gian mà Chênh lệch giữa SV = EV - PV Dương =

Sche tiến độ dự án sớm công việc hoàn Sớm tiến
dule hoặc trễ hơn thành tới một thời độ
varia ngày chuyển điểm, thường là
nce giao kế ngày dữ liệu, và Trung
hoạch, tại công việc kế hoạch bình =
một điểm cần hoàn thành tới Đúng
thời gian, thời điểm đó. tiến độ
biểu diễn
bằng chênh Âm =
lệch giữa giá Trễ tiến
trị thu được độ
và giá trị dự
kiến.

VAC Chênh lệch Dự báo số Chi phí chênh lệch VAC = BAC Dương =
khi hoàn tiền thâm hụt ước lượng tại lúc – EAC Dưới chi
Varia thành ngân sách hoàn thành dự án phí
nce hoặc thặng
at dư, thể hiện Trung
comp như sự khác bình =
letio biệt giữa Đúng chi
n ngân sách khi phí kế
hoàn thành hoạch
và ước tính
khi hoàn Âm =
thành. Vượt chi
phí kế
hoạch
CPI Chỉ số hiệu Một thước đo CPI là 1.0 có nghĩa CPI = EV/AC Lớn hơn
suất chi phí hiệu quả chi là dự án đang theo 1.0 =
Cost phí của đúng ngân sách, Dưới chi
perfo nguồn ngân công việc được phí
rman sách được thể thực hiện cho tới
ce hiện bằng tỷ hiện tại đúng ngân Bằng 1.0
index số giữa giá trị sách. Các giá trị = Đúng
thu được với khác thể hiện tỷ lệ chi phí
chi phí thực chi phí vượt quá kế hoạch
tế. hoặc dưới khoản
ngân sách cho công Nhỏ hơn
việc kế hoạch 1.0 =
Vượt chi
phí kế
hoạch

SPI Chỉ số hiệu Một thước đo SPI là 1.0 có nghĩa SPI = EV/PV Lớn hơn
suất tiến độ hiệu quả tiến là dự án đang theo 1.0 =
Sche độ thể hiện đúng tiến độ, công Sớm hơn
dule bằng tỷ số việc được thực hiện tiến độ
perfo giữa giá trị cho tới hiện tại
rman thu được và đúng theo kế Bằng 1.0
ce giá trị kế hoạch. Các giá trị = Đúng
index hoạch. khác thể hiện tỷ lệ tiến độ
chi phí vượt quá
hoặc dưới khoản Nhỏ hơn
ngân sách cho công 1.0 = Trễ
việc kế hoạch tiến độ

EAC Ước lượng Tổng chi phí Nếu CPI là không (1) EAC =
chi phí thực dự kiến để đổi trong thời gian BAC/CPI
Esti tế khi hoàn hoàn thành còn lại của dự án,
mate thành toàn bộ các EAC được tính
to công việc bằng (1):
comp được thể hiện
lete bằng tổng
các chi phí
thực tế tính
 đến thời điểm
hiện tại và và
ước tính đến
khi hoàn
thành.

EDA Ước lượng EDAC =

C tổng thời DAC/SPI
gian thực tế
Esti để hoàn
mate thành
durat
ion
to
comp
lete

ETC Ước lượng Chi phí dự Giả sử công việc ETC = EAC –
tới khi hoàn tính để hoàn đang theo kế hoạch, AC
Esti thành thành các chi phí để hoàn
mate công việc thành công việc còn
to còn lại của lại được tính bằng:
comp dự án. ETC =
lete Reestimate

Ước lượng lại công

việc còn lại từ dưới
lên.
Ví dụ về RACI Chart :waterfall – iterative incremental

R->A->C->I

Nếu là agile scrum thì thay role PM bên dưới -> Scrum master

PM- BA – UI/UX Senior Tester Product Customer

Project Business Designer Developer Owner
manag analysist
er

Create project C C C I A I
charter
R

Create SRS A R C C I I I
(software
requirement
specification )

Design I A R C I I I
wireframe

Implement A C C R C I I
coding

Perform testing A I I C R I I

Ví dụ về Product backlog

PRODUCT Back Log

As a .. i want to ... so that i can

 EPIC User story title User Story Acceptance criteria

Authentication More option to As an employee, I When user register to the

Feature log-in , register want to log-in system, the system will
through/via my automatically recommend
personal social the option “Register by
media account in email “
order to safe time
while logging in - With the user that
with no need to fill registered with email, they
in the password can log – in via email to safe
time and do not have to
enter password

Employee manage More health data As a manager, I want - When employee

controller in our employee to see more health register to the system, they
profile such as related data in our will be asked to give more
blood pressure, employee profile in specific information about
medical history order to manage their medical history
them better and give - This type of information
them proper job will be public in their profile

Ví dụ về smart goal

Smart goal 1 : Once our product released, it will be applied to 20% of all company in our city by the end
of the year

Specific : the team knows what they’re building : an app that helps employees care for their health and
reminds them to do so

Measurable : Once the app has been completed and sold to the market, it will be bought by at least 20%
of all company in local city

Attainable : Our team has a strong dev team, and a long-term sale and marketing strategy to develop this
product .

Relevant : This product will bring more revenue for our company

Time-bound : The team needs 4 months to complete this application and 6 months for marketing.
Smart goal 2: By the time our partner uses this product, it will be compatible with 100% employee in
their company

Specific: the team knows what they’re building : an app that helps employees care for their health and
reminds them to do so

Measurable : The product will be applicable when it includes 100% data of employees.

Attainable : Our team has a strong dev team, and a long-term sale and marketing strategy to develop this
product

Relevant : The administrator can manage their employee better by having their heath data .

Time-Bound : The team needs 4 months to complete this application

Request 3 Ví dụ về WBS – Kẻ bảng - ID, Task name , predecessor task

Task 3 : Iterative – incremental, each iteration includes a small waterfall model

FS -> finish to start

SF-> start to finish

SS-> start to start

FF -> finish to finish

ID TASK PREDECESSOR

1 Phase 1

1.1 Milestone: Initiating

1.1.1 Create Project charter 1.1.2SF

1.1.2 Get the project charter approval 1.1.1 FS

1.1.3 Kick-off meeting 1.1.2 FS

1.1.4 Create stakeholder Register 1.1.3SS

2 Phase 2

2.1 Milestone 2 : planning

2.1.1 Create Scope management plan

2.1.2 Create Schedule management plan 2.1.1 SS

2.1.3 Create Cost management plan 2.1.1SS

2.1.4 Create Risk management plan 2.1.1SS

2.1.5 Create Resource management plan 2.1.1SS

2.1.6 Create Communication management plan 2.1.1SS

2.1.7 Create Quality management plan 2.1.1SS

2.1.8 Create Stakeholder management plan 2.1.1SS

2.1.9 Create Procurement management plan 2.1.1SS

2.1.10 Create Change management plan 2.1.1SS

2.1.11 Meeting with the team to discuss about plan

2.1.12 Deliver project management plan

3 Phase 3

3.1 Milestone: Executing

3.1.1 Iteration 1

3.1.1.1 analysis

i . Create feasibility report

ii. Create use-case diagram and use-case description

iii. Create SRS documentation

3.1.1.2 Design

i. create design for wireframe

ii. create UI/UX design

iii. create mock-up screen

3.1.1 3 Implementing

i. implement coding for authentication

feature

ii. implement coding for employee

management controller
 3.1.1.4 Testing

i. Perform unit testing

ii. Perform integration testing

iii. Perform part of system testing

3.1.2 Iteration 2 :

3.1.2.1 analysis

i. Update feasibility report

ii. Update use-case diagram and use-case description

iii. Update SRS docs

3.1.2.2 Design

i. Update design for wireframe

ii. Update UI/UX design

iii. Update mock-up screen design

3.1.2.3 Implementing

i. implement coding for

recreational program controller

ii. implement coding for admin

role

3.1.2.4 Testing

i. Perform unit testing

ii. Perform integration testing

iii. Perform part of system testing

3.1.2 Iteration 3:

3.1.2.1 analysis

i. Update feasibility report

ii. Update use-case diagram and use-case description

iii. Update SRS docs

3.1.2.3 Design

iv. Update design for wireframe

v. Update UI/UX design

vi. Update mock-up screen design

3.1.2.5 Implementing

iii. implement coding for

healthcare program controller

iv. implement coding for

payment function

3.1.2.6 Testing

iv. Perform unit testing

v. Perform integration testing

vi. Perform system testing

vii. Perform acceptance testing

4 Phase 4
4.1 Milestone: Monitoring and controlling

4.1.1 Control scope

4.1.2 Track progress 4.1.1SS

4.1.3 Perform cost control 4.1.2SS

4.1.4 Monitor and control risk 4.1.3SS

5 Phase 5

5.1 Milestone : Closing

5.1.1 Create lesson learn

5.1.2 Create project final report

5.1.3 Close project ceremony