Participants at the 2004 USC-CSE Annual Research Review identified three
categories of real and perceived barriers to implementing agile processes.
Nonproblems
■ Quality assurance systems
■ Agile inadequate for managing defects
■ Refactoring is rework
■ Agile is monolithic
■ Quantitative management
■ Extension/effectiveness of automatic testing to acceptance/system integration
■ Perception that agile is extreme or a fad; not responsible
■ Agile projects are unmanaged
Problems only in terms of size or scope
■ Configuration management
■ Earned value tools: Agile focuses on features and business value, traditional
focuses on activities
■ Stakeholder sign-off requirements
■ Planning documentation
■ Deployment, life cycle support (training): Long-term life cycle sustainment,
decay rate of tacit knowledge
■ Risk management
■ Contracted/planned inch-pebble milestones
■ Process QA/standard processes
■ Process standards (IEEE, DoD, EIA)
■ Designing for the battle, not the war
Significant issues
■ Resource loading, slack, timekeeping, capital evaluation
■ Required colocation, customer access
■ Nonfunctional requirements
■ Documentation
■ Critical design reviews (milestones)
■ Contractual and source selection issues
■ Interfacing/integration with other methodologies/disciplines
■ Predictability, perfect knowledge
■ Statutory/regulatory constraints
■ HR policies and processes
■ System interface control
■ Roles, responsibilities, and skills
■ Agile work on legacy systems
■ Formal requirements
■ System engineering V-process model
■ Maturity assessments
■ Traditional engineering measurements
■ Cost estimation
Participants at the 2004 USC-CSE Annual Research Review identified three
categories of real and perceived barriers to implementing agile processes.
Nonproblems
■ Quality assurance systems
■ Agile inadequate for managing defects
■ Refactoring is rework
■ Agile is monolithic
■ Quantitative management
■ Extension/effectiveness of automatic testing to acceptance/system integration
■ Perception that agile is extreme or a fad; not responsible
■ Agile projects are unmanaged
Problems only in terms of size or scope
■ Configuration management
■ Earned value tools: Agile focuses on features and business value, traditional
focuses on activities
■ Stakeholder sign-off requirements
■ Planning documentation
■ Deployment, life cycle support (training): Long-term life cycle sustainment,
decay rate of tacit knowledge
■ Risk management
■ Contracted/planned inch-pebble milestones
■ Process QA/standard processes
■ Process standards (IEEE, DoD, EIA)
■ Designing for the battle, not the war
Significant issues
■ Resource loading, slack, timekeeping, capital evaluation
■ Required colocation, customer access
■ Nonfunctional requirements
■ Documentation
■ Critical design reviews (milestones)
■ Contractual and source selection issues
■ Interfacing/integration with other methodologies/disciplines
■ Predictability, perfect knowledge
■ Statutory/regulatory constraints
■ HR policies and processes
■ System interface control
■ Roles, responsibilities, and skills
■ Agile work on legacy systems
■ Formal requirements
■ System engineering V-process model
■ Maturity assessments
■ Traditional engineering measurements
■ Cost estimation
การแปล กรุณารอสักครู่..
