Principles | Glossary

Definition

Agile Manifesto has a set of 12 principles. They are as follows :

  • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software
  • Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage
  • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale
  • Business people and developers must work together daily throughout the project
  • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done
  • The most efficient and effective method of conveying information to and within a development team is face-to-face conversation
  • Working software is the primary measure of progress

 

Further Reading

  • “Understanding The Agile Manifesto: A Brief & Bold Guide to Agile” (book), by Larry Apke

 

Organization Chart | Glossary

Definition

Organizational Charts are created often by Corporate Managers. They are a set of slides that represent the company’s management structure and hierarchy. They act as templetization/ starting point in creating diagrams for the entire organization structure, and the different relationships between the positions and ranks.

As far as hierarchy in an Agile organization is concerned, it is overall less emphasized and communication overheads are minimised by the creation of semi-autonomous, cross-functional and self-organising teams. A single mid-level manager is usually capable to support 10-20 cross-functional teams.

Further Reading

  • “Organizational Design: A Step-by-Step Approach” (book), by Richard M. Burton.