Agile Software A Complete Guide - 2020 Edition. Gerardus Blokdyk. Читать онлайн. Newlib. NEWLIB.NET

Автор: Gerardus Blokdyk
Издательство: Ingram
Серия:
Жанр произведения: Зарубежная деловая литература
Год издания: 0
isbn: 9781867460480
Скачать книгу
next page of the Self-Assessment.

      Your completed Agile Software Scorecard will give you a clear presentation of which Agile Software areas need attention.

      Agile Software

      Scorecard Example

      Example of how the finalized Scorecard can look like:

      Agile Software

      Scorecard

      Your Scores:

      BEGINNING OF THE

      SELF-ASSESSMENT:

      Table of Contents

      About The Art of Service7

      Included Resources - how to access7

      Purpose of this Self-Assessment9

      How to use the Self-Assessment10

      Agile Software

      Scorecard Example12

      Agile Software

      Scorecard13

      BEGINNING OF THE

      SELF-ASSESSMENT:14

      CRITERION #1: RECOGNIZE15

      CRITERION #2: DEFINE:21

      CRITERION #3: MEASURE:33

      CRITERION #4: ANALYZE:41

      CRITERION #5: IMPROVE:52

      CRITERION #6: CONTROL:81

      CRITERION #7: SUSTAIN:90

      Agile Software and Managing Projects, Criteria for Project Managers:120

      1.0 Initiating Process Group: Agile Software121

      1.1 Project Charter: Agile Software123

      1.2 Stakeholder Register: Agile Software125

      1.3 Stakeholder Analysis Matrix: Agile Software126

      2.0 Planning Process Group: Agile Software128

      2.1 Project Management Plan: Agile Software131

      2.2 Scope Management Plan: Agile Software133

      2.3 Requirements Management Plan: Agile Software135

      2.4 Requirements Documentation: Agile Software138

      2.5 Requirements Traceability Matrix: Agile Software140

      2.6 Project Scope Statement: Agile Software142

      2.7 Assumption and Constraint Log: Agile Software144

      2.8 Work Breakdown Structure: Agile Software146

      2.9 WBS Dictionary: Agile Software148

      2.10 Schedule Management Plan: Agile Software151

      2.11 Activity List: Agile Software153

      2.12 Activity Attributes: Agile Software155

      2.13 Milestone List: Agile Software157

      2.14 Network Diagram: Agile Software159

      2.15 Activity Resource Requirements: Agile Software161

      2.16 Resource Breakdown Structure: Agile Software163

      2.17 Activity Duration Estimates: Agile Software165

      2.18 Duration Estimating Worksheet: Agile Software167

      2.19 Project Schedule: Agile Software169

      2.20 Cost Management Plan: Agile Software171

      2.21 Activity Cost Estimates: Agile Software173

      2.22 Cost Estimating Worksheet: Agile Software175

      2.23 Cost Baseline: Agile Software177

      2.24 Quality Management Plan: Agile Software179

      2.25 Quality Metrics: Agile Software181

      2.26 Process Improvement Plan: Agile Software183

      2.27 Responsibility Assignment Matrix: Agile Software185

      2.28 Roles and Responsibilities: Agile Software187

      2.29 Human Resource Management Plan: Agile Software189

      2.30 Communications Management Plan: Agile Software191

      2.31 Risk Management Plan: Agile Software193

      2.32 Risk Register: Agile Software195

      2.33 Probability and Impact Assessment: Agile Software197

      2.34 Probability and Impact Matrix: Agile Software199

      2.35 Risk Data Sheet: Agile Software201

      2.36 Procurement Management Plan: Agile Software203

      2.37 Source Selection Criteria: Agile Software205

      2.38 Stakeholder Management Plan: Agile Software207

      2.39 Change Management Plan: Agile Software209

      3.0 Executing Process Group: Agile Software211

      3.1 Team Member Status Report: Agile Software213

      3.2 Change Request: Agile Software215

      3.3 Change Log: Agile Software217

      3.4 Decision Log: Agile Software219

      3.5 Quality Audit: Agile Software221

      3.6 Team Directory: Agile Software224

      3.7 Team Operating Agreement: Agile Software226

      3.8 Team Performance Assessment: Agile Software228

      3.9 Team Member Performance Assessment: Agile Software230

      3.10 Issue Log: Agile Software232

      4.0 Monitoring and Controlling Process Group: Agile Software234

      4.1 Project Performance Report: Agile Software236

      4.2 Variance Analysis: Agile Software238

      4.3 Earned Value Status: Agile Software240

      4.4 Risk Audit: Agile Software242

      4.5 Contractor Status Report: Agile Software244

      4.6 Formal Acceptance: Agile Software246

      5.0 Closing Process Group: Agile Software248

      5.1 Procurement Audit: Agile Software250

      5.2 Contract Close-Out: Agile Software253

      5.3 Project or Phase Close-Out: Agile Software255

      5.4 Lessons Learned: Agile Software257

      Index259

      CRITERION #1: RECOGNIZE

      INTENT: Be aware of the need for change. Recognize that there is an unfavorable variation, problem or symptom.

      In my belief, the answer to this question is clearly defined:

      5 Strongly Agree

      4 Agree

      3 Neutral

      2 Disagree

      1 Strongly Disagree

      1. Do you need quantum computing to create human level AI?

      <--- Score

      2. How much flexibility does your software need?

      <--- Score

      3. How do scaling issues affect the manner in which you fulfill your goal of identifying your initial scope?

      <--- Score

      4. Do you need quantum computing for consciousness?