Talk:Software Engineering Guide

From PDune

[edit] Draft proposal for...

Note: For the moment, we focus on Scrum and agile methodologies (usually applicable to...

• small-medium teams (can be aggregated into bigger ones, but require further techniques)
• unstable (by nature or due to lack of information) => difficult to plan
• available customers and users

[edit] Main Disciplines

• Project Management
  • Is a support discipline (not directly productive)
  • Aims to provide control through direction (->) and predictability (<-)
  • Tasks:
    • Strategic Planning: (goals, stakeholders, priorization, control settings, ...)
    • Resource (budget, knowledge, effort, methods&tools ...) management (estimations, negotiation, usage control, ...)
    • Tactical planning: (scheduling, assignments, ...)
    • Follow up & reporting (of all other tasks' results)
    • Risk & Incident management
    • Learning
  • Types:
    • Creative Project (once)
    • Service Project (continuous)
    • Agile projects use to be a mix of those 2

• Product Development
  • Is a core discipline (directly productive)
  • Aims to create/improve the tools to solve the need/generate the seeked value
  • Phases:
    • Requirement analysis and specification
    • Solution analysis: conceptual > logic
    • Implementation
  • Other tasks:
    • Root Cause Analysis (RCA) / Problem (root) solving

• System Operation = Service Delivery
  • Is the core discipline (absolutely productive)
  • Aims to generate the actual seeked value
  • Phases:
    • System deployment/Product roll out (delivery preparation)
    • System exploitation (service delivery)
    • System retirement (service phase out)
  • Tasks
    • Incident Management / Troubleshooting / Patching
    • Change Control
    • Service Desk & Reporting

[edit] Other (sub)Disciplines

• QA Management (Project Management)
  • Is a support (sub)discipline.
  • Aims to provide control through direction (->) and predictability (<-)
  • QA Promotion
    • QA Planning
    • QA Consulting
    • Training
  • QA Control
    • Product Verifications
      • Unit testing
      • Integration testing
      • Functional testing
      • Regression testing
      • Code inspections
    • Random testing & product validation
    • Process Cerifications
      • CheckPoints
      • Automatic reports & metrics
      • Process audits
    • Process & tools validations
      • Test runs / Null series
      • Polls & Feedback gathering

• Change Management
  • Risk Assessment & Analysis
  • Impact Assessment& Analysis
  • Configuration Control Strategy Setting/Planning
    • Systems/environments
    • CI (Configuration Items) Classification (on nature and timeline)
    • CI Flow Rules (on events)
  • Release Management
  • Deployment Management (Decission taking)

• Resources (effective and efficient) Usage Control and Accountability
  • Is a support (sub)discipline.
  • Aims to provide control through direction (->) and predictability (<-)
  • Asset Management
    • Inventories
    • Likely Usage Planning (Estimations, Ruling, ...)
    • Actual Usage Control
  • Investion Working capital (OpEx vs. CapEx)
    • H.RR (manpower, skills, ...)
    • Budget ($, t)
    • Tools
    • Materials
    • Processes, know-how, ...
  • Results/ Quality (Balanced ScoreCard: finals, intermediate, internals, mood...)
    • Production
    • Stakeholders' Satisfaction
    • Underlying quality (quality of internal use, subproducts, ...)
    • Waste, iterations, false alarms, reworks, difficulties, ...