CMMI Process Area Level 2 Manajemen Proses STTI i-Tech Nov 2014
Materi Kuliah • CMMI PA Level 2 : Manajemen Proses • Key Process Area • Manajemen Proyek • Software Development Process
SW CMM Level 2 • Some software development processes are repeatable, possibly with consistent results. • Specific project’s processes may differ
• The organization may use some basic project management to track cost, schedule, and functionality to identify problems meeting requirements. • When these practices are in place, projects are performed and managed according to their documented plans.
• Project status and the delivery of services are visible to management at defined points. • for example, at major milestones and at the completion of major tasks
• Basic project management processes are established to track cost, schedule, and functionality. • The minimum process discipline is in place to repeat earlier successes on projects with similar applications and scope. • There is still a significant risk of exceeding cost and time estimates.
CMM Level 2 Key Process Areas (KPA) • • • • • •
Requirements Management (RM) Software Configuration Management (CM) Software Project Planning (PP) Software Project Tracking and Oversight (PT) Software Subcontract Management (SM) Software Quality Assurance (QA)
Introduction about the sample of processes • Written to address the KPA of Level 2. • Represent some early steps toward addressing these KPA but do not necessarily meet every key practice.
• Consider to be a "starter set" to begin continuous process improvement using the CMM as a guideline. • Not intended to be implemented directly in another organization, but they can be used as a basis for discovering what will work and deciding what can be implemented in your organization.
Project Management • Components • Project Management Policy • Purpose • Scope • Policy –objectives to be achieved
• Project Management Processes
Project Management • Components • Project Management Policy • Purpose • Scope • Policy –objectives to be achieved
• Project Management Processes
Project Management Policy: Purpose • To provide direction for using these project management process • Project Level Processes • • • •
Requirements Management Process Project Planning Process Estimation Process Project Tracking Process
• Business Unit Level Processes • • • •
Commitment Control Process Project Management Review Process Software Quality Assurance Process Project Management Processes Overview
Project Management Policy: Scope • Applies to all projects that meet the following criteria: • The project commitment is external to the business unit and either • exceeds $20K of departmental resources or • exceeds 10 elapsed weeks.
Project Management Policy : in Requirements Management • The requirements are documented. • The requirements are reviewed by managers and affected groups. • When requirements change, project plans, deliverables, and activities are also changed.
Project Management Policy Objectives in Software Project Planning • The requirements and estimates are the basis of project plans. • Commitments are negotiated among the project manager, department manager, director, and managers of affected groups. • Interdependencies with other business units are negotiated and documented. • Affected groups review project plans and estimates. • The director reviews all commitments made external to the business unit. • The project plans are documented, managed, and controlled.
Project Management Policy Objectives in Software Project Tracking and Oversight • The project plans are the basis for project tracking and are maintained to current status. • The project manager is kept informed of the project status and issues. • Corrective actions are taken when the project plan is not being achieved, either by adjusting performance or by adjusting the plan. • Changes to commitments are renegotiated with all affected parties.
Project Management Policy Objectives in Software Quality Assurance • The SQA function is performed on all projects. • Those performing SQA activities are independent of the project's management reporting chain. • The director and department managers periodically review SQA activities and results.
Project Management Policy Objectives in Software Configuration Management • SCM responsibility is explicitly assigned. • SCM is implemented throughout the life cycle. • SCM is implemented for all externally deliverable software products, designated internal software deliverables, and designated support tools (such as compilers). • The projects have the ability to store the elements under SCM. • The software baselines and SCM activities are audited on a periodic basis.
Project Management • Components • Project Management Policy • Purpose • Scope • Policy –objectives to be achieved
• Project Management Processes
Project Management Process: Overview • How the project management processes work together to form a management system directed toward meeting software delivery commitments. • The Roles in the Organization: • • • • • •
Director Department Manager Project Manager Project Team Member Program Manager (Marketing perspectives) SEPG Software Engineering Process Group (SQA Team)
• A Software Engineering Process Group (SEPG) is an organization's focal point for software process improvement activities. These individuals perform assessments of organizational capability, develop plans to implement needed improvements, coordinate the implementation of those plans, and measure the effectiveness of these efforts. Successful SEPGs require specialized skills and knowledge of many areas outside traditional software engineering.[1]
• Obtains and maintains the support of all levels of management. • Facilitates software process assessments. • Works with line managers whose projects are affected by changes in software engineering practice, providing a broad perspective of the improvement effort and helping them set expectations. • Maintains collaborative working relationships with software engineers, especially to obtain, plan for, and install new practices and technologies. • Arranges for any training or continuing education related to process improvements.
• Tracks, monitors, and reports on the status of particular improvement efforts. • Facilitates the creation and maintenance of process definitions, in collaboration with managers and engineering staff. • Maintains a process database. • Provides process consultation to development projects and management.
Project Management Process: Objectives • To establish basic management processes to track size, cost, schedule, and functionality and establish the necessary process discipline.
Conceptual Flow of Processes • Management System Processes Pyramid:
To Meet Commitments • It is necessary to: • • • • • •
Understand REQUIREMENTS ESTIMATE the work PLAN the work so that the original commitment is achievable Control the COMMITMENT approvals TRACK status against the plans REVIEW status toward commitments and initiate changes if necessary • ASSURE product quality and process compliance and initiate corrective action if necessary • Control CONFIGURATION of deliverables and records
Top-Down View • Initial commitments are supported by project plans, which in turn are supported by requirements and estimation activities. • After initial commitments are made, commitment status monitoring is supported by reviews, which in turn are supported by tracking and assurance activities.
Bottom-Up View • Requirements are gathered and estimates of the work effort are made. • The results feed into plans, and the plans receive commitment approval. • Then the plans are tracked, and the products and processes are assured. • The results feed into reviews, and reviews report status or issues on progress toward commitments.
The Role of Configuration Management • To prevent loss of important project information such as deliverables and records
Process Flow • Shows the interaction and flow between the processes. • More details about the process steps can be found in each process document.
• The process begins with a request to the business unit to provide some functionality. This may be indicated by: • a Program Statement from marketing, • a request from another business unit with an interdependency, or • a Custom Engineering Request.
Quality Records (QR) • QR – the documents that report and demonstrate use of the process. • Where process problems exist, the quality records may indicate the need for process improvement. • For the supported life of the product.
• Project notebooks are set up to store the records. • The record fields: Notebook section, document record, controlling process, traceability to KPA/key practice.
• The other records are maintained for the organization wide processes. • The records associated to their controlling group.
Processes di dalam CMMI • • • • • • •
Requirement Management Process Project Planning Processes Estimation Process Commitment Control Process Project Tracking Process Project Management Review Process SQA Process
KPA Goals terhadap Proses dari Requirement Management • KPA: System requirement dialokasikan tehadap software dan dikendalikan untuk membangun baseline dalam manajemen dan pengembangan perangkat lunak • Process: Requirements Management
• KPA: Rencana Software, produk dan aktivitas tetap konsisiten terhadap system requirements yang dialokasikan terhadap software. • Process: Requirements Management, Project Planning
KPA Goals terhadap proses dari Project Planning • KPA: Estimasi Software didokumentasikan untuk digunakan dalam perencanaan dan tracking project software. • Process: Estimation
• KPA: Project Software aktifitas dan komitmen direncakanan dan didokumentasikan • Processes: Project Planning, Commitment Control
• KPA: Kelompok dan individu yang terkena dampak setuju terhadap komitmen yang berkaitan dengan software project. • Process: Commitment Control
KPA Goals terhadap proses dari Project Tracking • Actual result dan performance dilacak terhadap rencana software. • Process: Project Tracking
• Mengambil tindakan korektif dan dimanage untuk closure ketika actual result dan performance menyimpang secara significant terhadap rencana software • Processes: Project Tracking, Project Management Reviews
• Perubahan terhadap komitmen software disetujui ketika berdampak pada kelompuk atau individu • Process: Commitment Control
KPA Goals terhadap proses dari Configuration Management • Aktifitas Manajemen konfigurasi software direncanakan. • Process: Project Planning
• Work product software yang terpilih diidentifikasi, dikontrol dan tersedia • Process: Project Planning
• Perubahan terhadap work produk software diidentifikasi dan di control. Dampak terhadap kelompok dan individu diinformasikan berupa status dan isi dari software baselines. • Process: Prosedur terpisah untuk release proses dan tools
KPA Goals to Processes: Subcontract Management • Kontraktor memilih subkontraktor yang berkualitas • Kontraktor dan subkontraktor setuju untuk berkomitmen satu dengan yang lainnya • Kontraktor dan subkontraktor software setuju untuk menjaga komunikasi yang sedang berlangsung • Kontraktor akan melacak actual result dari subkontraktor dan performance terhadap komitmen yang telah dibuat • Semua Proses diatas : prosedur terpisah dalam kebijakan dan pedoman perusahaan
TUGAS • Di dalam project management, hal apa saja yang dikelola didalamnya. Jelaskan. Siapa yang bertugas dalam mengelola project? • Hal apa saja yang harus selalu dijaga dan dimonitor didalam project sehingga dapat selalu inline dengan jadwal dan cost? • Apa yang menjadi pertimbangan utama dibutuhkannya implementasi Manajemen Proses dari KPA 2 CMMI ini? Jelaskan secara terinci. • Tahapan apa yang harus dijalankan didalam Software Project Planning? Jelaskan • Jelaskan setiap item didalam Management System Process Pyramid
