Agile Concepts
Reference URL: https://www.toptal.com/project-managers/agile/project-management-blueprint-part-1-agile-scrum-kanban-lean
Changes to requirements are welcomed, even late in the development.
Frequent cycles of delivery
Stakeholder collaboration
A culture of trust, support and motivation.
Self-organising teams
Self-reflection, continuous improvement and sustainable development.
Simplicity & productivity – the art of maximizing the amount of work not done is essential.
Examples of scrum: Extreme Programming, Scrum, Kanban.
Welcoming changeing requirements, even late in development - The Agile Way
The whole rational behind an agile approach to software project management is NOT about being faster. It is about being able to adapt well to new situations.
When a client asks for a change in something that was already delivered or is even being developed, our first reaction so to become upset and think “Why didn’t they think about it before asking?” However, after a while, we realize that change is actually for the best as it will increase the value to the whole product a lot. The client will be more satisfied and end users will benefit.
Better Success: Agile projects are 28% more successful than traditionally managed projects.
Providing Value: A common adage in the IT industry is that, 80% of all end users generally only use 20% of a software application’s features. Agile addresses this by focusing on creating the Minimum Viable Product (MVP) by delivering the minimum set of features that will deliver perceived value to users.
Reduce Complexity: By breaking down the typical long cycle of a traditional project into four week cycles, called iterations, Agile Project Delivery reduces project risk and complexity with iterations, containing small, user-ready segments of the final product.
The Four values of Agile Project Delivery.