FIVE MAIN PROJECT STAKEHOLDER:

 Agile/Scrum:

- Scrum master: A Scrum Master chiefly acts as a coach and facilitator to the Scrum
Team. He helps the team to assign user stories with top priority into sprints.
- Product owner: External stakeholder, Accountable for the whole system,
responsibility for defining requirement, responsibility for defining scope for each
sprint and each scrum team
 Iterative incremental/ Waterfall/ Vmodel
- Project manager: Internal stakeholder, planning and organizing, managing tasks,
budgeting, controlling costs, scope and other factors. Everything they do helps make
sure the project can be completed on time and on budget, and more importantly,
profitable.
 CÒN LẠI:
- 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.
- 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.
RACI – FIVE STACKS OR DELIVERABALES
 Iterative incremental/ Waterfall/ Vmodel
Create project charter: PM(R), BA(C), Dev(C), Tester (C), Customer (C)
Create SRS: PM(A), BA(R), Dev(C), Tester (C), Customer (C/R)
Create BD: PM(A), BA(R), Dev(C), Tester (I/C), Customer (C)
Create DD: PM(A), BA(C), Dev(R), Tester (I/C), Customer (C)
Implement coding: PM(A), BA(C), Dev(R), Tester (C), Customer (I)
Test case: PM(A), BA(R), Dev(C), Tester (R), Customer (C)
Perform testing: PM(A), BA(I), Dev(C), Tester (R), Customer (I)
 Agile/Scrum:

Create project backlog: Scrum Master(C), BA(C), Dev(C), Tester (I), Product owner(R/A)
Create Sprint backlog: Scrum Master(R), BA(C), Dev(C), Tester (I), Product owner(A)
Create BD: Scrum Master(C), BA(R), Dev(C), Tester (I), Product owner(A)
Implement coding: Scrum Master(C), BA(C), Dev(R), Tester (C), Product owner(A)
Perform testing: Scrum Master(C), BA(I), Dev(C), Tester (R), Product owner(A)
FIVE PROJECT SMART GOALS
Smart Goal 1: Implement a fully automated synchronization process to ensure that all
(người nhận quyền lợi) information from (tên web/app)is accurately and securely
transferred to the new (tên công ty) learning platform within 24 hours of the data being
available.

Specific (S): This goal specifies the need for synchronization of (người nhận quyền lợi)
information from (tên web/app) to the new learning platform.

Measurable (M): The goal is measurable based on the time frame of 24 hours for data
synchronization.

Attainable (A): Given the advancements in data integration and automation technologies,
implementing an automated synchronization process within 24 hours of data availability is
feasible.

Relevant (R): Accurate and timely student information synchronization is crucial for a seamless
(tên người nhận quyền lợi) experience and efficient administrative processes.
Time-bound (T): The project needs (thời gian hoàn thành dự án) to conduct the development
phase . The goal has a specific time frame of 24 hours, ensuring timely transfer of data between
the admissions website and the learning platform.

Smart Goal 2: Increase (tên người nhận quyền lợi)engagement in (tên app/web) by 20%
within the next time.

Specific (S): This goal is specific as it focuses on a particular metric, which is (tên người nhận
quyền lợi).

Measurable (M): The goal is measurable as it aims for a 20% increase, providing a clear and
quantifiable target.

Attainable (A): The goal is achievable within a time through targeted strategies like interactive
content, discussion forums, and real-time assessments.

Relevant (R): This goal is relevant to the overall improvement of the system, aligning with (tên
công ty) aim to enhance the quality.
Time-bound (T): The goal has a specific time frame, which is within the next time, making it
time-bound and providing a clear deadline.

Smart Goal 3: Attain a 95% (người nhận quyền lợi) satisfaction rate with the platform by
the conclusion of the year.

Specific (S): The goal specifies the objective of achieving a high (tên người nhận quyền lợi)
satisfaction rate with (tên web/app).

Measurable (M): The goal is measurable based on the satisfaction rate, aiming for 95%.
Attainable (A): By addressing feedback, enhancing user experience, and continually improving
the platform, a 95% satisfaction rate is attainable.

Relevant (R): High (người nhận quyền lợi)satisfaction with the platform is relevant to the
overall success of the (tên công ty)
Time-bound (T): The goal's timeframe is set for the end of the academic year, making it time-
bound.

Smart Goal 4: Reduce 15% abandonment rate (web/app name) in the near future.

Specific (S): The goal is clear in its focus on the abandonment rate in (web/app name) .

Measurable (M): The 15% reduction provides a measurable target to track progress.

Achievable (A): By implementing better (tên người nhận quyền lợi) support systems, proactive
outreach, and improved design, a 15% reduction is a realistic and achievable goal.

Relevant (R): Reducing abandonment rates (tên web/app) is related to improving the system.
Time-bound (T): The goal's timeframe is set for the upcoming year, making it time-bound.

Smart Goal 5: Increase the utilization of online assessment tools by 30% in the next
quarter.

Specific (S): The goal focuses on the increased utilization of a specific feature - online
assessment tools.

Measurable (M): The goal is measurable, targeting a 30% increase in utilization, which can be
tracked.

Achievable (A): By leveraging the benefits of online review tools, providing customers, and
integrating reviews a 30% increase is achievable.

Relevant (R): Improving the use of online assessment tools aligns with (tên công ty) goal to
enhance the experience and streamline evaluation processes.

Time-bound (T): The goal has a defined timeframe of one quarter, making it time-bound and
ensuring prompt action.

FIVE PROJECT RISKS

Risk 1: The team lack the required skills for website testing.
Possibility: High
Impact: Moderate
Mitigation plan: Plan training course to skill up your member
Risk 2: Wrong budget estimate and cost overruns.
Possibility: Moderate
Impact: Extreme
Mitigation plan: Establish the scope before beginning work, pay a lot of attention to project
planning and constantly track and measure the progress by EVM.
Risk 3: The project schedule is too tight; it’s hard to complete this project on time.
Possibility: High
Impact: High
Mitigation plan: Set Test priority for each of the activity.
Risk 4: Project manager has poor management skill.
Possibility: Moderate
Impact: Moderate
Mitigation plan: Plan leadership training for manager
Risk 5: A lack of cooperation negatively affects your member productivity.
Possibility: Moderate
Impact: Moderate
Mitigation plan: Encourage each team member in his task, and inspire them to greater efforts.
WBS: 4 – 5 LEVELS
 Iterative incremental/ Waterfall/ Vmodel
1. TÊN DỰ ÁN – level 1
1.1 Phase 1: Initiating (level 2)
1.1.1 Create project proposal
1.1.2 Create Project Charter (level 3)
1.1.2.1 Solidifying the project scope (level 4)
1.1.2.2 Determine resources needed (level 4)
1.1.2.3 Define project SMART goal and deliverables (level 4 )
1.1.3 Get project charter approval (level 3)
1.1.4 Hold a kick-off meeting (level 3)
1.1.5 Perform a cost - benefit analysis for the project- - level 3
1.1.6 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 Schedule 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 4)
1.2.2 Meeting with team to discuss about plans (level 4)
1.2.3 Deliver Project Management Plan (level 4)

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

Iteration 1 – Level 3
1.3.1 Requirement Analysis (level 4)
1.3.1.1 Create Feasibility Report (level 5)
1.3.1.2 Create Business requirement specification (level 5)
1.3.1.3 Create SRS for module 123 (level 5)
1.3.1.4 Perform Requirement validation (level 5)
 1.3.1.5 Perform Requirement management (level 5)
1.3.2 Design (level 4)
1.3.2.1 Create Basic design for module 1 (level 5 )
1.3.2.2 Create detail design for module 1 (level 5 )
1.3.3 Implementing (level 4)
1.3.3.1 Implement code for module 1
1.3.4 Testing (level 4)
1.3.4.1 Create test plan test case
1.3.4.2 Perform unit testing for module 1 (level 5)
1.3.4.3 Perform integration testing for module 1 (level 5)
Iteration 2 –( level 3 )
1.3.5 Requirement Analysis (level 4)
1.3.5.1 Update Feasibility Report (level 5)
1.3.5.2 Update Business requirement specification (level 5)
1.3.5.3 Update SRS (level 5)
1.3.6 Design (level 4)
1.3.6.1 Create Basic design for module 2 (level 5 )
1.3.6.2 Create Detail design for module 2 (level 5)
1.3.7 Implementing (level 4)
1.3.7.1 Update coding for module 1 : (level 5)
1.3.7.2 Implement coding for module 2 (level 5)
1.3.8 Testing (level 4)
1.3.8.1 Create test plan test case
1.3.8.2 Perform unit testing (level 5)
1.3.8.3 Perform integration testing (level 5)
1.3.8.4 Perform part of system testing for modul 1-2 (level 5)
Iteration 3 – level 3
1.3.9 Requirement Analysis (level 4)
1.3.9.1 Update Feasibility Report (level 5)
1.3.9.2 Update Business requirement specification (level 5)
1.3.9.3 Update SRS (level 5)
1.3.10 Design (level 4)
1.3.10.1 Create Basic design for module 3 (level 5)
1.3.10.2 Create Detail design for module 3 (level 5 )
1.3.11 Implementing (level 4)
1.3.11.1 Update coding for module 1,2 : (level 5)
1.3.11.2 Implement coding for module 3 : (level 5)
1.3.12 Testing (level 4)
1.3.12.1 Perform unit testing (level 5)
1.3.12.2 Perform integration testing (level 5)
1.3.12.3 Perform system testing (level 5)
1.3.12.4 Perform acceptance testing (level 5)
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)
 Agile/Scrum:
TÊN DỰ ÁN – 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

USER STORIES” As a….i want to… So That…”

As an administrator, I want to see more health-related data in our employee profiles in order to manage
them better and give them the proper job.

User story detail: 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.
User story detail: As a project manager I want to create and update the WBS and inform the WBS to
stakeholder so as to manage and share WBS.
DEFINED- ALL THE PATH
Determine / Define the duration of this project / Define the minimum duration to complete all the
deliverable
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
19week is the duration of the project
duration of the project is the longest path
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
DẠNG TÍNH TOÁN KHÓ VỠI KHÔNG HIỂU