Software Development Approaches and Agile Methodologies

Software Development Approaches

• Software development has evolved significantly over 70+ years, with various models and methodologies used.
• Models are customized to meet specific needs rather than being implemented as-is.
• Each model possesses advantages and drawbacks.

Understanding Agile

• Agile is a "best-of-breed" collection of methodologies for software development and maintenance.
• Agile projects emphasize flexible roles, with team members able to take on multiple roles and evolve their roles over time.
• Roles in agile are not fixed positions.
• Agile de-emphasizes specialized roles, recognizing all team members as equals involved in delivering a solution.

Stakeholder Roles

• Stakeholders are individuals impacted by the project's outcome, exceeding the scope of just end-users.
• Stakeholders may include users, user managers, senior managers, operations/IT staff, project funders, auditors, developers of integrated systems, and maintenance personnel.

Product Owner

• The Product Owner represents the voice of stakeholders to the development team.

• They clarify solution details and maintain a prioritized backlog of tasks for implementation.

• The Product Owner is responsible for timely answers and keeps the team focused on tasks.

• Communicates project status and represents the team to stakeholders.

• Defines project strategy, goals, and direction.

• Translates customer and stakeholder needs into actionable requirements.

• Prioritizes and manages these requirements.

• Manages the project budget and profitability.

• Determines release dates for completed features/functionality.

• Answers questions and makes decisions with the development team.

• Accepts or rejects completed work during sprints.

• Presents team accomplishments at the end of each sprint.

Team Member Roles

• Team members focus on producing the solution.
• Their tasks include testing, analysis, architecture, design, programming, and planning, potentially more.
• Team members possess varying skills and strive to gain more throughout the project.
• Team members identify, estimate, commit to, and track the completion of tasks.

Team Lead Role

• The Team Lead manages team processes.
• They act as a servant-leader, supporting teamwork and focused delivery.
• Facilitate communication, teamwork processes, and resource management.
• Responsible for issue resolution.
• Act as an agile coach, particularly for new teams needing mentorship.

Architecture Owner

• The Architecture Owner ensures architecture decisions mitigate project risks.
• Facilitates the creation and evolution of the overall project design.
• In smaller teams, the team lead often fulfills this role.

Agile Mentor/Coach

• Agile mentors/coaches provide guidance and feedback to project teams.
• They are often external to the organization, offering objective guidance.
• Experienced in agile techniques and implementing them across diverse projects.

Secondary Agile Roles

• Domain Expert: Possesses deep business/industry knowledge exceeding that of the Product Owner.
• Specialist: Specialized roles such as business analysts, or project/program managers.
• Technical Expert: Added as needed to address complex technical issues, mentoring team members.
• Independent Tester: Working independently validating work throughout the life cycle.
• Integrator: Responsible for integrating various subsystems into a complete system.