Agile Project Management Overview

Agile Project Management

• Organizational Cultures & Styles:

  • Shared vision, mission, and values are important.
  • Risk tolerance is crucial for innovation.
  • Code of conduct, work ethics, and work hours are key.
  • Operational environment must be supportive.

• Organizational Communication:

  • Effective communication is a key factor in successful projects.
  • Communication between stakeholders and the project team is essential.

• Organizational Structures:

  • Functional structure: managed by functional managers.
  • Weak matrix: less power to project managers.
  • Balanced matrix: more balanced power.
  • Strong matrix: more power to project managers.
  • Project-based: project manager responsible.
  • Composite: mixed approach of functional and project-based.

• Structure's Function in Software Development:

  • Junction structure: project manager taking decisions.
  • Coordinator: limited freedom, responsible for coordinating the work.
  • Expediator: coordinates the work in the projects.

• Project organization:

  • Projectized organization: projects are classified and assigned to projects.
  • Composite organization: mixed functional and project-based.
  • Balanced matrix: combines functional structure with project-based management.

• Organizational Process Assets:

  • Processes and procedures should be clear and well-documented.
  • Templates, standards, and knowledge bases help streamline work.
  • Historical information and lessons learned are valuable resources.

• Enterprise Environmental Factors:

  • Organizations must consider internal and external factors that affect projects.
  • These factors include infrastructure, HR skills, market conditions, and political climate.

Project Life Cycle (PLC)

• Project Team:

  • Individuals working together to complete projects.

• Project Life Cycle (PLC) Phases:

  • A series of phases from start to end.
  • Phases are determined by the project.

• Important PLC Considerations:

  • Predictive/Plan Driven: detailed plans upfront.
  • Iterative & Incremental: build incrementally throughout the development process.
  • Adaptive/Change Driven (Agile): flexible approaches to changes.
  • Starting: the first stage of a project.

• Predictive Life Cycle Models:

  • Waterfall model
  • Prototyping

Agile Project Management Benefits

• Agile Project Management Benefits:

  • Better product quality.
  • Higher customer satisfaction.
  • More control over the project.
  • Reduced project risks.
  • Faster ROI.

• Agile Team:

  • Self-empowered teams.
  • Effective teamwork.
  • Adaptable to change.

• Agile Advantages:

  • Visibility for constant feedback.
  • Project flexibility, adaptability to changing requirements.
  • Risk reduction in projects when facing challenges.
  • Clear understanding of project value and business goals during the project.
  • Agile triangle (Scope, Time, Cost).

Agile Software Development

• Agile Software Development Methods:

  • XP, Scrum, DSDM, Adaptive software development
  • Crystal, FDD

• Reasons for Agile Methodology:

  • Ambiguity in requirements necessitates frequent adaptation.
  • Changes are inevitable; iterative approaches are more effective.
  • Frequent reflections, adjustments, and small improvements.
  • Frequent feedback, small steps for better control during development.

• Manifesto for Agile Software Development:

  • Focus on individuals and interactions.
  • Working software over comprehensive documentation.
  • Customer collaboration over contract negotiation.
  • Responding to change over following a plan