Team Assignment 3 Team 4 – K15T2 Present. Introduce to project Goal of project Profitable for...
-
Upload
emil-lawson -
Category
Documents
-
view
216 -
download
0
description
Transcript of Team Assignment 3 Team 4 – K15T2 Present. Introduce to project Goal of project Profitable for...
Team Assignment 3Team 4 – K15T2 Present
Introduce to projectGoal of project Profitable for Honda Vietnam Company. Improved working process. Increases the friendly, quality customer
service of Honda Vietnam. Uses less than human. reference profile, pricing, reports ... fast and
accurately, saving work time.
Introduce to projectProject deliveries Source code Product backlog Sprint backlog Project plan Test plan
Project organizer
Scrum process support to develop the complex products ,rapid-prototyping project.
There are 3 basic element in scrum: Clear Inspectable Flexible
Roles
Change Manage Process
Change Control Board ( CCB )Change Type Reason Solutions Priority
Technical Connection
Connection method is not effective
Use another conection method more effective and make sure a minimal change can occur in source code
Low
SDK library
SDK doesn’t supportRemove unsuitable SDK, repair, re-install or install new SDK.
Low
Change Control Board ( CCB )Change Type Reason Solutions Priority
Internal
RulesChange the rules by changing business
requirements
The group discussed whether the new rules are not suitable for group or proposed solutions or to comply with new rules to make the group come up.
Low
Document
Initially the project team is prepared to carefully document these deviations in the software development
If the influence of small construction materials that the project team can repair even if it is affecting the quality of software project teams that will make future sprint.
High
Goal Changes consistent with group goals
Identify new goals, if appropriate target group members will set out the appropriate direction to meet the new target .Unless appropriate to go omitted schedule to help implement the other goals.
High
Change Control Board ( CCB )Change Type Reason Solutions Priority
InternalProcess
Process is adapted not well to team.
Scrum master, leader find the problem why adapting the process to team
High
Human Resource
Human lost ( illness, have other important works, … )
Work of that member will be break and assign for another members in team
High
Lack of code, test, write document skill Organize training people
High
New human is added or change human in current team
Scrum Master support new member to have good communication with others, support him to know what to do.
Low
Change Control Board ( CCB )Change Type Reason Solutions Priority
External
Requirement
Development team causes change
Validating the affect.
Negotiate with customer
Cancel sprint if not success in negotiating.
High
Customer deletes the requirement
Product owner will evaluate the impact of the requirement be dropped for the remaining requirements.Then remove that requirement from the product backlog
Low
Schedual Working time of the members have a large difference compared to the estimated time
Scrum master must find the cause of the delay deadline and update previous estimates
High
Risk Manage Process
Thanks for your listening