The Agile Frameworks for Developers
Agile software development is a set of ideas and priorities about software development and how to manage projects. At its core, Agile is more philosophical than it is practical. With the Agile Manifesto, the 12 principles of Agile, Agile gives an overview of how things should be done. However, Agile does not give details and specifics for a project. Part of the beauty of Agile is how adaptable it is. Software development organizations are all different, and Agile has something that each of them can use.
This is where Agile frameworks come in. An Agile framework is basically a more practical implementation of Agile concepts. These frameworks deal with more of the “how,” and less of the “why.” Organizations that choose to use Agile already know why they want to, they just need a better idea of how to implement Agile in a way that fits their own situation. Each Agile framework has certain priorities, and certain cases or industries in which it works better or worse.
Scrum
Of all the Agile Frameworks, Scrum is one of the most popular. One of the most beneficial elements of Scrum is its scalability. Both large and small projects can use Scrum methods equally well. This is accomplished in large part by implementing a “scrum of scrums” where necessary. Each individual team works on its own backlog, but these teams can coordinate in larger organizations to work toward a larger and more complex goal.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course:
Course Contents
Section 1: Agile Project Management
Section 2: Using the Agile Manifesto to Deliver Change
Section 3: The 12 Agile Principles
Section 4: The Agile Fundamentals
Section 5: The Declaration of Interdependence
Section 6: Agile Development Frameworks
Section 7: Introduction to Scrum
Section 8: Scrum Projects
Section 9: Scrum Project Roles
Section 10: Meet the Scrum Team
Section 11: Building the Scrum Team
Section 12: Scrum in Projects, Programs & Portfolios
Section 13: How to Manage an Agile Project
Section 14: Leadership Styles
Section 15: The Agile Project Life-cycle
Section 16: Business Justification with Agile
Section 17: Calculating the Benefits With Agile
Section 18: Quality in Agile
Section 19: Acceptance Criteria and the Prioritised Product Backlog
Section 20: Quality Management in Scrum
Section 21: Change in Scrum
Section 22: Integrating Change in Scrum
Section 23: Managing Change in Scrum
Section 24: Risk in Scrum
Section 25: Risk Assessment Techniques
Section 26: Initiating an Agile Project
Section 27: Forming the Scrum Team
Section 28: Epics and Personas
Section 29: Creating the Prioritised Product Backlog
Section 30: Conduct Release Planning
Section 31: The Project Business Case
Section 32: Planning in Scrum
Section 33: Scrum Boards
Section 34: Sprint Planning
Section 35: User Stories
Section 36: User Stories and Tasks
Section 37: The Sprint Backlog
Section 38: Implementation of Scrum
Section 39: The Daily Scrum
Section 40: The Product Backlog
Section 41: Scrum Charts
Section 42: Review and Retrospective
Section 43: Scrum of Scrums
Section 44: Validating a Sprint
Section 45: Retrospective Sprint
Section 46: Releasing the Product
Section 47: Project Retrospective
Section 48: The Communication Plan
Section 49: Formal Business Sign-off
Section 50: Scaling Scrum
Section 51: Stakeholders
Section 52: Programs and Portfolios