1. Context
  2. Myths and realities: why agile?
  3. Agile approach
  4. Why should we adopt agile?
  5. Agile vs. traditional

  1. Agile principles and values
  2. Disadvantages of the traditional approach
  3. The “traditional” management approach
  4. The “agile” management approach
  5. Agile work process for projects

  1. Framework of methodologies
  2. FDD, DSDM and Lean
  3. Scrum
  4. XP methodology
  5. “5 S” methodology

  1. The definition of Kanban
  2. Examples of the task boards
  3. Designing the Kanban board
  4. Using the Kanban inside the iteration
  5. Sinergy of methodologies

  1. Business case. Project justification
  2. Customer-centric approach. Declaration of inter-dependence
  3. Project vision
  4. Knowledge management areas according to the agile approach
  5. The 'personas' technique

  1. Prioritization of requirements based on business value
  2. Refining priorities
  3. User stories
  4. Splitting requirements
  5. Agile management of requirements

  1. Done” and “ready”
  2. Common mistakes
  3. Adaptive planning
  4. Agile estimation of requirements
  5. Velocity, timebox, and establishing the process

  1. Roadmap
  2. Adjusting the roadmap
  3. Limitation of work in progress
  4. Validity of the agile approach
  5. Change management

  1. Release plan
  2. Use of the release plan
  3. Iteration zero and Spikes
  4. Preparing the iteration
  5. Iteration planning

  1. Detailing the iteration content
  2. Deadline, cost and people
  3. Iteration. Implementation and closing
  4. Agile engineering practices
  5. Other ways of estimating and planning

  1. Earned Value traditional method
  2. Earned value in lean construction projects
  3. Agile earned value
  4. Monitoring the team
  5. High performance teams

  1. Monitoring the work
  2. Demo or review meeting
  3. Retrospective meeting
  4. Information radiators
  5. Project closure