Software Lifecycle Methodology and Quality Manager

1. Experience:

Minimum 6 years of experience in the field of software development, software quality, or technological project management.

Minimum 4 years of experience in functions related to:

Definition of methodologies, frameworks, or software development standards.

Software quality assurance throughout the lifecycle (SDLC).

Proven experience in:

Design and implementation of procedures, guides, and software development best practices.

Definition of quality criteria, control points, and verification mechanisms.

Monitoring of methodological compliance in development projects.

Coordination with internal technical teams and external software development providers.

Experience in multi-vendor environments, involving different development companies with heterogeneous approaches.

Experience working with large organizations, preferably in the public sector or highly regulated environments.

Experience in:

Definition of common frameworks to be required in contracts or specifications.

Homogenization, standardization, or governance projects for software development.

Environments with a low initial level of maturity in methodology and quality.

Certifications and specific training (recommended).

Certifications in software quality or processes, such as:

ITIL (especially oriented towards service and quality management).

Certifications related to quality models or processes (ISO, CMMI, SPICE, or others).

2. Project management certification, preferably:

PMP or equivalent.

Agile certifications (Scrum Master, PMI-ACP, SAFe, or others), from a governance perspective.

(A purely Agile or purely traditional profile is not sought, but rather one with an integrative and pragmatic vision).

3. Specific training in:

Software Development Lifecycle (SDLC).

Software quality assurance and control.

Process definition and improvement.

Technological vendor management.

Organizational change management.

Training in technical and methodological documentation.

4. Technical and methodological knowledge

Solid knowledge of:

Full software development lifecycle.

Quality models and development best practices.

Requirements management, testing, validation, and acceptance.

Ability to define:

Minimum development standards.

Mandatory deliverables.

Acceptance and quality criteria.

Knowledge of environments where developments are mostly carried out by third parties.

5. Personal skills and competencies

Global and strategic vision, with the ability to define common and sustainable frameworks over time.

Structuring and synthesis capacity, oriented towards creating clear, understandable, and applicable methodologies.

Ability to influence without hierarchy, promoting the adoption of the methodology in internal teams and providers.

Rigor, method, and quality orientation, without losing pragmatism.

Communication skills, both technical and executive.

Orientation towards continuous improvement.

Pedagogical capacity, to explain, accompany, and facilitate the adoption of best practices.

Autonomy and professional judgment, with a service-oriented approach to the organization.

Years of experience in the position: Greater than 5 years.

Degree: Computer Science, Computer Engineering.

1. Definition and establishment of the software lifecycle quality methodology

Define and maintain a corporate software development and quality methodology that covers the entire lifecycle (analysis, design, construction, testing, deployment, and maintenance).

Establish common standards, procedures, guides, and templates for software development projects.

Define quality criteria, control points, and validation mechanisms throughout the lifecycle.

Align the methodology with recognized best practices (ISO, quality models, development frameworks), adapting them to the context of the public organization.

Ensure that the methodology is practical, applicable, and scalable, avoiding excessively theoretical approaches.

2. Governance and homogenization of software developments

Act as a corporate reference for software development and quality best practices.

Reduce the heterogeneity of approaches, technical solutions, and quality levels among projects and providers.

Establish a common framework that allows for comparability, reuse, and sustainability of developments.

Define minimum mandatory criteria for external provider companies regarding methodology and quality.

3. Promotion, implementation, and adoption of the methodology

Disseminate the methodology among internal teams and external providers.

Accompany projects during the progressive implementation of the methodology.

Prepare support materials (practical guides, checklists, recommendations).

Drive the adoption of a culture of quality and continuous improvement in software development.

Resolve methodological doubts and act as a point of reference for project teams.

4. Monitoring and control of methodological compliance

Define and execute monitoring mechanisms for compliance with the methodology in projects.

Perform periodic quality reviews and control points throughout the lifecycle.

Identify deviations, risks, and areas for improvement in developments.

Propose and monitor corrective actions when necessary.

Provide status and maturity information to project managers and management.

5. Continuous improvement and evolution of the methodological framework

Analyze lessons learned and project results to improve the methodology.

Periodically update the methodological framework based on technological and organizational evolution.

Propose improvements that increase the efficiency, quality, and maintainability of developments.

Contribute to the definition of a medium- and long-term software quality strategy.