ISO 12207 provides a framework for the entire lifecycle of software from inception to retirement, detailing processes such as analysis, design, implementation, testing, and maintenance . Conversely, the Capability Maturity Model (CMM) categorizes the maturity levels of these processes, determining how systematically they are defined, managed, and improved . Together, these models complement each other by offering guidelines (ISO 12207) and a maturity evaluation framework (CMM) to continuously improve software processes.

In-house project management involves managing projects with internal staff, leveraging internal expertise, and resources which offer direct control over project scope, quality, and timelines. This approach provides better alignment with organizational culture and objectives . Contract project management, in contrast, relies on external vendor expertise for construction and delivery, which may introduce varying levels of control and consistency but is beneficial for accessing specialized skills and reducing internal workload . The choice depends on resource availability and strategic objectives.

Agile methodologies offer improved flexibility, customer collaboration, and incremental delivery of software, which can adapt better to changes and evolving requirements . However, Agile can be challenging due to potential scope creep and the need for high involvement from stakeholders and clients. On the other hand, Waterfall provides a structured approach with clear documentation and requirements phase, which helps in projects with fixed requirements but lacks flexibility, making it inefficient in managing changing customer needs . The choice between these approaches depends on the project context and stakeholder requirements.

Ethical and professional concerns impact software development practices by influencing team behavior, client interactions, and product integrity. Ethical practices ensure software safety, security, and reliability, thereby maintaining user trust and legal compliance . Professional conduct fosters team collaboration, transparency, and accountability, enhancing project outcomes by ensuring stakeholder expectations are fairly managed and met. Ignoring these concerns can lead to project failures, legal repercussions, and damage to reputation.

Creating a Work Breakdown Structure (WBS) is crucial because it breaks down a project into smaller, manageable components, ensuring comprehensive coverage of project tasks and facilitating better resource allocation, time management, and budget estimation . It provides a hierarchical decomposition of the project scope, clarifying responsibilities and delivering a detailed project outline that helps in tracking progress and ensuring all parts are covered without overlapping or missing tasks.

The decision to build or purchase software hinges on considerations such as cost, time, scalability, customization needs, and resource availability. Purchasing off-the-shelf software typically offers faster deployment and lower initial costs but may lack customization. Building software allows for tailored solutions that meet specific business requirements but involves higher costs and longer development time . Cost-benefit analysis plays a critical role by evaluating these factors over the expected lifecycle of the software, helping in calculating long-term benefits compared to the investment and operational costs.

Principles of project management processes provide a structured approach to executing, managing, and closing projects, ensuring objectives such as scope, cost, and timing are met. They include defining project objectives, structuring phases, resource allocation, stakeholder engagement, and risk management . These principles enforce accountability and provide a framework for decision-making and benchmarking progress, ensuring that deliverables align with organizational goals and client expectations.

Strategic programme management focuses on achieving strategic objectives through a series of related projects and initiatives that contribute to major organizational change . It emphasizes long-term goals, benefits realization, and change management. Project portfolio management, on the other hand, involves selecting, managing, and controlling a collection of projects that align with strategic objectives, ensuring resource optimization and maximizing returns . While both align with organizational goals, programme management has a longer-term, broad impact focus, whereas portfolio management deals with immediate project efficacy and resource alignment.

Agile software development prioritizes customer satisfaction by involving customers in the developmental process through frequent deliveries and iterative reviews, thus ensuring alignment with their needs and expectations . Agile's inherent adaptability to change is maintained by flexible planning, continuous stakeholder collaboration, and regular adaptation of plans to suit evolving requirements, thereby reducing time-to-market and empowering teams to respond effectively to changes throughout the project lifecycle.

Risk management in software project management involves the identification, analysis, and mitigation of potential project risks to increase the likelihood of project success . Effective integration into project planning involves a proactive approach to risk identification and ranking, allowing for crafting mitigation strategies and contingency plans early in the project lifecycle. This ensures that risks are monitored and controlled through strategies outlined in steps such as a step-wise project plan , thereby mitigating potential project threats and optimizing project outcomes.