Manajemen Proyek TI

Diskusi Case Study PM Process Groups

Bagus Pribadi - 1706043941

Nabilla Yuli Shafira - 1706984682
Rahmadian Tio Pratama - 1706044074
Steffi Alexandra - 1706043992

SISTEM INFORMASI

FAKULTAS ILMU KOMPUTER

UNIVERSITAS INDONESIA

2019
Proses Agile Approach Predictive Approach

Pre-Initiation Tasks Activities: Activities :

● Determine roles
● Decide how many ● Defining the
sprints will compose high-level scope of
each release and the the project
scope of software to ● Identify the project
deliver (project sponsor
scope) ● Select the project
● Create a survey that manager
specifically asks ● Determining whether
potential user which there is a strong
features would business case for
provide the most the project or not. If
value there isn’t, the
● A team member project won’t
create one to four continue.
designs of a ● Hold the meeting to
particular interface review the process
for prospective user and expectations for
to review managing the project
● Determine if the
project should be
divided into smaller
projects
● Draft a business
case and get inputs
and feedbacks for it

Output :
● Business case
● Business scope
● List of project
sponsors

Initation Activities :
● Drafting the project
charter
● Identify stakeholders
● Holding a project
kick-off meeting

Outputs :
● Project charter
● Stakeholder register

Planning Activities: Activities :

● Create team ● Create team contract
contract, WBS Gantt ● Plan scope
chart, and a list of management
 prioritized risks for ● Collect requirements
the whole project ● Define scope
(project scope, cost, ● Create work
time) breakdown structure
● Product owner (WBS)
create product ● Plan schedule
backlog management
● Project team,create ● Define activities
sprint backlog ● Sequence activities
● Create release ● Estimate activity
backlog resources
● Plan work each day ● Estimate activity
in the daily scrum durations
● Document stumbling ● Develop schedule
blocks in a list ● Plan risk
● Provide the basis for management
time estimates for ● Identify risks
the sprint planning ● Perform qualitative &
meeting (project quantitative risk
time) analysis
● Provide a clear ● Plan risk response
picture of what
stories (scope) will Outputs :
be contained in each ● Team contract
sprint ● Requirement
● Create a release management plan
road map ● Requirement
documentation
Outputs: ● Requirement
● Team contract traceability matrix
● WBS ● Project scope
● List of prioritized statement
risks ● Scope baseline
● Product backlog ● Risk management
● Sprint backlog plan
● Road map ● Risk register
● User stories
● Gantt chart

Executing Activities: Activities :

● Produce several ● Acquire project team
iterations of a ● Develop project
potentially team
shippable-product at ● Manage project team
the end of each ● Manage
sprint communication
● Users would be able between team
to make suggestions members
for functionality ● Conduct
● Meeting with the procurement when
 scrum master the resources are
available
Output: ● Manage stakeholder
● Product backlog engagement
● Sprint backlog ● Create milestone
● Templates reports
● Samples Output :
● Project schedules ● Project staff
● Sprint backlog assignments
● WBS’s ● Resource calendars
● Point person for user ● Project management
stories plan updates
● Team performance
assessment
● Enterprise
environmental factor
updates
● Change request
● Project document
updates
● Organizational
process assets
updates
● Milestone report
● Selected sellers
● Agreements
● Issue log

Monitoring & Activities: Activities :

Controlling ● Resolve Risk, Issues ● Monitor and control
and blockers project work
● Create and update ● Perform integrated
burndown chart change control
● Demonstrate the ● Control costs
complete product ● Control
during the sprint communications
review meeting ● Control risks
● Meeting with the ● Control procurement
scrum master ● Control stakeholder
● Plan and engagement
communicate work
of the day Output :
● ● Work performance
Output: reports
● Burndown chart ● Approved change
● The ScrumMaster request
documents issues ● Change logs
and blockers ● Work performance
and information
● Cost forecast
Closing Activities: Activities :
● ScrumMaster Leads ● Gaining stakeholder
a sprint retrospective and customer
● Solicits team acceptance
member feedback ● Bring the project to
via email an orderly end
● Meeting with ● Require staff to
ScrumMaster support the intranet
● Suggest to improve site
the project and ● Created a transition
process during the plan
sprint retrospective ● Deliver the final
meeting product
● Demonstrate ● Update
Output: organizational
● Lessons-learned process assets
report ● Prepared a final
● List of action items report, final
for implementation presentation,
● Product backlog contract files, and
● Release of useful lessons-learned
software report
● Wrote summary
lessons-learned
report
● Sign a client
acceptance form
Output :
● Final project report
● Presentation
● Final product
● Project files
● Lessons-learned
report
● Contract files
● Final documentation