Week 4 – Planning & Managing Projects #1 Software Engineering Week 4 – Planning & Managing Projects #1 A.A. Gde Bagus Ariana, S.T. gungariana@yahoo.com http://gungariana.wordpress.com
Content Management activities Project planning Project scheduling Critical Path Method (CPM) Program Evaluation and Review Technique (PERT)
WHY??? Software project management Ensuring that software is delivered on time and on schedule Software development is always subject to budget and schedule constraints Mengapa kita sangat memerlukan manajemen proyek? Memastikan perangkat lunak terinstal di end-user tepat waktu dan sesuai jadwal Pembangunan perangkat lunak selalu bersubjek pada budget/anggaran dan batasan2 jadwal
Management Activities Proposal writing. Project planning and scheduling. Project costing. Project monitoring and reviews. Personnel selection and evaluation. Report writing and presentations. Ini adalah aktivitas2 yang dilakukan oleh pihak manajemen
Project planning Probably the most time-consuming project management activity. Continuous activity from initial concept through to system delivery. Plans must be regularly revised as new information becomes available. Membuat rencana proyek mungkin merupakan aktivitas yang paling banyak menghabiskan waktu saat projek manajemen aktiviti
Types of project plan Quality Plan Validation Plan Describes the quality procedures and standards that will be used in a project. Validation Plan Describes the approach, resources and schedule used for system validation. Types of project plan Configuration Management Plan Describes the configuration management procedures and structures to be used. Maintenance Plan Predicts the maintenance requirements of the system, maintenance costs and effort required. Staff Development Plan Describes how the skills and experience of the project team members will be developed.
Project Plan Resource Work Breakdown Schedule
Project plan structure Introduction. Project organisation. Risk analysis. Hardware and software resource requirements. Work breakdown. Project schedule. Monitoring and reporting mechanisms.
Activity organization Activities in a project should be organised to produce tangible outputs for management to judge progress. Milestones are the end-point of a process activity. Deliverables are project results delivered to customers. The waterfall process allows for the straightforward definition of progress milestones. Berikut adalah beberapa aktivitas organisasi, Tangible = nyata, tidak muluk2 Milestones = tonggak sejarah (translate), end-point atau titik akhir dari sebuah proses Deliverables = hasil proyek harus dikirim/diinstal ke customer Metode waterfall yang memungkinkan adanya milestones
Activities and Milestones Feasibility Study Requirement Analysis Prototype Development Design Study Requirement Specification Feasibility Report User Requirement Evaluation Report Architectural Design System Requirement Yang warna biru = aktivitas Yang warna hijau = milestone
Project scheduling Split project into tasks and estimate time and resources required to complete each task. Organize tasks concurrently to make optimal use of workforce. Minimize task dependencies to avoid delays caused by one task waiting for another to complete. Dependent on project managers intuition and experience.
The project scheduling process
Work Breakdown
Anatomy of a Project STEP 1 ACTIVITY 1.1 PHASE 1 ACTIVITY 1.2 : PHASE 2 PHASE n STEP 1 STEP 2 ACTIVITY 2.1 ACTIVITY 2.2 ACTIVITY 3.3
Anatomy of a Project
Scheduling problems Estimating the difficulty of problems and hence the cost of developing a solution is hard. Productivity is not proportional to the number of people working on a task. Adding people to a late project makes it later because of communication overheads. The unexpected always happens. Always allow contingency in planning. Contingency = hal yang kebetulan
Bar charts and activity networks Graphical notations used to illustrate the project schedule. Show project breakdown into tasks. Tasks should not be too small. They should take about a week or two. Activity charts show task dependencies and the critical path. Bar charts show schedule against calendar time.
Task durations and dependencies
Activity network
Activity timeline
Staff allocation
Project Personnel Have to consider workforce Role Ability Experience etc… Task not performed by the same person Dependent on: Project size Staff expertise & experience Decide roles decide type of people To determine the project schedule and estimate the effort and costs the number of people working on the project, their role in the project, ability and experience etc. are required to be known. Not every task is performed by the same person or group; the assignment of staff to tasks depends on the project size, staff expertise and experience. After deciding on the roles for the personnel, next is deciding the type of people suited in the role.
Work Styles Extrovert tells others his thoughts Introvert asks others for suggestions Intuitive base decisions on feelings & emotions Rational examine facts & carefully considering all options Different people have different styles for interacting with others on the job and with understanding problems that arise in the course of their work. Extrovert - is a person who tells others his thoughts. Introvert - is a person who asks others for suggestions. Intuitive people base their decisions on feelings about and emotional reactions to a problem Rational people decide by examining facts and carefully considering all options.
Work Styles Rational extroverts Rational introverts Assert their ideas Not let “gut feeling” affect their decision Based on logic & not emotions Rational introverts Avoid emotional decisions Willing to consider all possible courses of action Rational extroverts tend to assert their ideas and not let “gut feeling” affect their decision making and it is based on logic and not emotions. Rational introverts also avoid emotional decisions but they are willing to take time to consider all possible courses of action. Intuitive extroverts base many decisions on emotional reaction, tending to want to tell others about them, rather than asking for input. Intuitive introverts is creative but applies creativity after having gathered sufficient information on which to base a decision.
Work Styles Intuitive extroverts Intuitive introverts Based on emotional reaction Want to tell others about them No asking of input Intuitive introverts Creative Applies it after lengthy analysis & findings Rational extroverts tend to assert their ideas and not let “gut feeling” affect their decision making and it is based on logic and not emotions. Rational introverts also avoid emotional decisions but they are willing to take time to consider all possible courses of action. Intuitive extroverts base many decisions on emotional reaction, tending to want to tell others about them, rather than asking for input. Intuitive introverts is creative but applies creativity after having gathered sufficient information on which to base a decision.
Project Personnel Intuitive Introvert Intuitive Extrovert Asks Others Tell Others Acknowledge feelings Acknowledge feelings Rational Introvert Rational Extrovert Asks Others Tells Others Decides logically Decides logically RATIONAL INTUITIVE EXTROVERT INTROVERT
Critical Path Method (CPM)
Critical Path Method Analysing paths among milestones Find out minimum completion time Outlines critical activities Allows estimation of real time/actual time estimated amount of time required for the activity to be completed. Allows identification of available time amount of time available in the schedule for the activity’s completion Deterministic method that uses a fixed time estimate for each activity
Program Evaluation and Review Technique (PERT)
PERT Program Evaluation and Review Technique (PERT) network model that allows for randomness in activity completion times Network of boxes (activities) & arrows (dependencies) Boxes can be used as milestones Critical path similar meaning to CPM
Tugas Membuat Resume ttg CPM dan PERT, tulis tangan di kertas double folio, bahasa indonesia yang baik dan benar. Untuk mahasiswa yang mengambil RPL hari Senin, berikut adalah referensi untuk tugas: http://www.youtube.com/watch?v=DdDzybQ_9vM Referensi lain yang berbahasa indonesia yang relevan. Buat tugas dengan sebaik-baiknya. Kumpul : 15 Oktober 2012, tidak ada toleransi keterlambatan. (jika tidak bisa hadir karena sakit/ijin, titip kepada teman)