Software As A Secure Service A Complete Guide - 2020 Edition - Gerardus Blokdyk

Скачать книгу

and round to the nearest tenth. Then transfer to the corresponding spoke in the Software As A Secure Service Scorecard on the second next page of the Self-Assessment.

      Your completed Software As A Secure Service Scorecard will give you a clear presentation of which Software As A Secure Service areas need attention.

      Software As A Secure Service

      Scorecard Example

      Example of how the finalized Scorecard can look like:

      Software As A Secure Service

      Scorecard

      Your Scores:

      BEGINNING OF THE

      SELF-ASSESSMENT:

      Table of Contents

      About The Art of Service8

      Included Resources - how to access8

      Purpose of this Self-Assessment10

      How to use the Self-Assessment11

      Software As A Secure Service

      Scorecard Example13

      Software As A Secure Service

      Scorecard14

      BEGINNING OF THE

      SELF-ASSESSMENT:15

      CRITERION #1: RECOGNIZE16

      CRITERION #2: DEFINE:28

      CRITERION #3: MEASURE:45

      CRITERION #4: ANALYZE:59

      CRITERION #5: IMPROVE:76

      CRITERION #6: CONTROL:93

      CRITERION #7: SUSTAIN:105

      Software As A Secure Service and Managing Projects, Criteria for Project Managers:130

      1.0 Initiating Process Group: Software As A Secure Service131

      1.1 Project Charter: Software As A Secure Service133

      1.2 Stakeholder Register: Software As A Secure Service135

      1.3 Stakeholder Analysis Matrix: Software As A Secure Service136

      2.0 Planning Process Group: Software As A Secure Service138

      2.1 Project Management Plan: Software As A Secure Service141

      2.2 Scope Management Plan: Software As A Secure Service143

      2.3 Requirements Management Plan: Software As A Secure Service145

      2.4 Requirements Documentation: Software As A Secure Service147

      2.5 Requirements Traceability Matrix: Software As A Secure Service149

      2.6 Project Scope Statement: Software As A Secure Service151

      2.7 Assumption and Constraint Log: Software As A Secure Service153

      2.8 Work Breakdown Structure: Software As A Secure Service155

      2.9 WBS Dictionary: Software As A Secure Service157

      2.10 Schedule Management Plan: Software As A Secure Service160

      2.11 Activity List: Software As A Secure Service162

      2.12 Activity Attributes: Software As A Secure Service164

      2.13 Milestone List: Software As A Secure Service166

      2.14 Network Diagram: Software As A Secure Service168

      2.15 Activity Resource Requirements: Software As A Secure Service170

      2.16 Resource Breakdown Structure: Software As A Secure Service172

      2.17 Activity Duration Estimates: Software As A Secure Service174

      2.18 Duration Estimating Worksheet: Software As A Secure Service176

      2.19 Project Schedule: Software As A Secure Service178

      2.20 Cost Management Plan: Software As A Secure Service180

      2.21 Activity Cost Estimates: Software As A Secure Service182

      2.22 Cost Estimating Worksheet: Software As A Secure Service184

      2.23 Cost Baseline: Software As A Secure Service186

      2.24 Quality Management Plan: Software As A Secure Service188

      2.25 Quality Metrics: Software As A Secure Service190

      2.26 Process Improvement Plan: Software As A Secure Service192

      2.27 Responsibility Assignment Matrix: Software As A Secure Service194

      2.28 Roles and Responsibilities: Software As A Secure Service196

      2.29 Human Resource Management Plan: Software As A Secure Service198

      2.30 Communications Management Plan: Software As A Secure Service200

      2.31 Risk Management Plan: Software As A Secure Service202

      2.32 Risk Register: Software As A Secure Service204

      2.33 Probability and Impact Assessment: Software As A Secure Service206

      2.34 Probability and Impact Matrix: Software As A Secure Service208

      2.35 Risk Data Sheet: Software As A Secure Service210

      2.36 Procurement Management Plan: Software As A Secure Service212

      2.37 Source Selection Criteria: Software As A Secure Service214

      2.38 Stakeholder Management Plan: Software As A Secure Service216

      2.39 Change Management Plan: Software As A Secure Service218

      3.0 Executing Process Group: Software As A Secure Service220

      3.1 Team Member Status Report: Software As A Secure Service222

      3.2 Change Request: Software As A Secure Service224

      3.3 Change Log: Software As A Secure Service226

      3.4 Decision Log: Software As A Secure Service228

      3.5 Quality Audit: Software As A Secure Service230

      3.6 Team Directory: Software As A Secure Service233

      3.7 Team Operating Agreement: Software As A Secure Service235

      3.8 Team Performance Assessment: Software As A Secure Service237

      3.9 Team Member Performance Assessment: Software As A Secure Service239

      3.10 Issue Log: Software As A Secure Service241

      4.0 Monitoring and Controlling Process Group: Software As A Secure Service243

      4.1 Project Performance Report: Software As A Secure Service245

      4.2 Variance Analysis: Software As A Secure Service247

      4.3 Earned Value Status: Software As A Secure Service249

      4.4 Risk Audit: Software As A Secure Service251

      4.5 Contractor Status Report: Software As A Secure Service253

      4.6 Formal Acceptance: Software As A Secure Service255

      5.0 Closing Process Group: Software As A Secure Service257

      5.1 Procurement Audit: Software As A Secure Service259

      5.2 Contract Close-Out: Software As A Secure Service261

      5.3 Project or Phase Close-Out: Software As A Secure Service263

      5.4 Lessons Learned: Software As A Secure Service265

      Index267

      CRITERION #1: RECOGNIZE

      INTENT:

Скачать книгу