Agile

IBF: Agile 

  • Competency Unit 1: Agile
    • Understand the value of Agile and the different methodologies of Agile
    • Understand the drivers and process of implementing agile in an organisation (e.g. business outcome and impact, centricity, capabilities, people)
  • Competency Unit 2: Experimental Mindset
    • Understand experimental mindset and the value of adopting experimental process
    • Application of tools in the execution
  • Competency Unit 3: Business Model Canvas
    • Understand the different components of Business Model Canvas and how they relate to each other
    • Application of Business Model Canvas

Agile

Video Intro

Agile

Value

Agile Value

  • Individuals and Interactions
  • Working Software
  • Customer Collaboration
  • Responding to Change
  • Processes and Tools
  • Comprehensive Documentation
  • Contract Negotiation
  • Following a Plan

Source: Manifesto

Agile

12 Principles

  1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
  3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  4. Business people and developers must work together daily throughout the project.
  5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  1. Working software is the primary measure of progress.
  2. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  3. Continuous attention to technical excellence and good design enhances agility.
  4. Simplicity--the art of maximizing the amount of work not done--is essential.
  5. The best architectures, requirements, and designs emerge from self-organizing teams.
  6. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.

Agile

Another View

Title Text

  • Bullet One
  • Bullet Two
  • Bullet Three

Title Text

Business Model Canvas

Source: Link

Title Text

Canvanizer

Source: Link

Source: Link

Lean Canvas Model

Title Text

Source: Link

Lean vs BMC

Design Thinking, Lean and Agile

Design Thinking, Lean and Agile

At a distance, Design Thinking is a mindset for exploring complex problems or finding opportunities in a world full of uncertainty. It’s a search for meaning, usually focusing on human needs and experience. Using intuitive and abductive reasoning, Design Thinking explores and questions what is, and then imagines what could be with innovative and inventive future solutions.

 

The Lean mindset is a management philosophy that embraces scientific thinking to explore how right our beliefs and assumptions are while improving a system. Lean practitioners use the deliberate practice of testing their hypotheses through action, observing what actually happens, and making adjustments based on the differences observed. It’s how organizations set their course, learn by doing, and decide what to do next on their journey to achieve outcomes.

 

The heart of Agile is building great software solutions that adapt gracefully to changing needs. Agile begins with a problem—not a requirement—and delivers an elegant solution. The Agile mindset acknowledges that the right solution today might not be the right solution tomorrow. It’s rapid, iterative, easily adapted, and focused on quality through continuous improvement.

Agile

By Anthony Ng