Linked e-resources
Details
Table of Contents
Part I: The Role of the Leader
1. The Role of the Leader
2. A few words about complexity
3. To the Manifesto!- 4. Using the Agile Manifesto as a framework
Part II: Leadership in Todays Technology Organizations
5. What is leadership?- Part III. Why Change the Way We Lead?- 6. Employee expectations are changing
7. The way work gets done is changing
Part IV: The Twelve Principles of the Agile Manifesto
8. Agile Principle 1: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software."
9. Agile Principle 2: Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage."
10. Agile Principle 3: Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale."
11. Agile Principle 4: Businesspeople and developers must work together daily throughout the project."
12. Agile Principle 5: Build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done."
13. Agile Principle 6: The most efficient and effective method of conveying information to and within a development team is face-to-face conversation."
14. Agile Principle 7: Working software is the primary measure of progress.
15. Agile Principle 8: Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
16. Agile Principle 9: Continuous attention to technical excellence and good design enhances agility.
17. Agile Principle 10: Simplicity
the art of maximizing the amount of work not done
is essential.
18. Agile Principle 11: The best architectures, requirements, and designs emerge from self-organizing teams.
19. Agile Principle 12: At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly..
1. The Role of the Leader
2. A few words about complexity
3. To the Manifesto!- 4. Using the Agile Manifesto as a framework
Part II: Leadership in Todays Technology Organizations
5. What is leadership?- Part III. Why Change the Way We Lead?- 6. Employee expectations are changing
7. The way work gets done is changing
Part IV: The Twelve Principles of the Agile Manifesto
8. Agile Principle 1: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software."
9. Agile Principle 2: Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage."
10. Agile Principle 3: Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale."
11. Agile Principle 4: Businesspeople and developers must work together daily throughout the project."
12. Agile Principle 5: Build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done."
13. Agile Principle 6: The most efficient and effective method of conveying information to and within a development team is face-to-face conversation."
14. Agile Principle 7: Working software is the primary measure of progress.
15. Agile Principle 8: Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
16. Agile Principle 9: Continuous attention to technical excellence and good design enhances agility.
17. Agile Principle 10: Simplicity
the art of maximizing the amount of work not done
is essential.
18. Agile Principle 11: The best architectures, requirements, and designs emerge from self-organizing teams.
19. Agile Principle 12: At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly..