A framework for software process models in governmental IT projects
Main elements of the V-Modell XT framework
Project types
Decision points
Project implementation strategies
Process modules
References
Rational Unified Process (RUP)
An industrial framework for software process models
Phases of the RUP
1. Inception
2. Elaboration
3. Construction
4. Transition
Scrum
An evolutionary process model framework characterized by consistent organization in short cycles and a self-organizing team
Central roles in Scrum
Product Owner
Scrum Master
Team
Product Owner
Represents the needs of the customer or the user, responsible for the success of the project and requirements engineering
Team
Responsible for the technical conception, construction, and quality assurance of the software, works in a self-organized and autonomous manner
Scrum Master
Comparable to an organizational project manager, moderates and accompanies the activities in Scrum, ensures adherence to time and organizational requirements
Product backlog
List of all system requirements, ranging from initial ideas to fully specified functions, prioritized by the Product Owner
Sprint backlog
List of requirements to be implemented by the team in a sprint, a subset of the product backlog
Velocity
Team-specific key figure indicating how many and which requirements a team can load from the product backlog into a sprint backlog
Phases of a Scrum sprint
1. Sprint planning
2. Sprint
3. Sprint review
4. Sprint retrospective
Organization-specific software process models are created based on these frameworks, which then serve as specifications for individual software development projects
