What is and Agile and Scrum Methodology or Framework? What are the framework options and which one is best suited to your project? Lets take a look at some of the available frameworks.
The Agile Frameworks
A 59 Seconds Agile Video Animation
Agile and Scrum Methodology or Framework and The Developer
A 59 Seconds Agile Article
What are Agile Frameworks and which is best suited for your project. The choice of Agile Frameworks depends on many factor, each framework has its own benefits. Lets take a look at a selection of the most popular frameworks to help you choose which is best for you.
Agile and Scrum Methodology or Framework: Priorities
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.
Agile and Scrum Methodology or Framework: 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.
Another facet that allows Scrum to have such scalability is its rhythm over time. Other Agile frameworks may be geared specifically toward small, short projects. For Scrum projects, teams find a certain pace and can typically keep this pace over long spans of time. This means that teams can work on short projects, but they can similarly continue working for months or even years to accomplish much larger goals.
Developers on Scrum teams are part of a bigger operation. While they are not like interchangeable cogs in the larger machine which is how traditional methods treat developers, Scrum developers are able to shift between features as necessary. Between sprints, if priorities shift, developers can be assigned completely new tasks to work on for the next software release.
Another popular Agile framework, Feature-Driven Development or FDD starts at the finished product that it seeks to create and works backward. FDD creates a process that will create the desired product feature by feature. Unlike other frameworks that may shift priority frequently within the same project, FDD typically takes a direction and pursues a feature or set of features until it is finished. How do you eat an elephant? One bite at a time.
Developers on FDD teams can typically get comfortable with a specific feature. Unlike other frameworks that may have developers change features any time stakeholders shift priorities, FDD developers can expect to continue working on features to their completion.
Agile and Scrum Methodology or Framework: Crystal Clear
Crystal Clear Agile is unique in that it focuses on people more than other frameworks. The 6 core components of Crystal Clear are people, interaction, community, communication, skills, and talents. Nothing in that list is specific to software development, so it is a project management style that can be applied across many industries.
User Stories Applied
A 59 Seconds Agile Book Review
User Stories Applied by Mike Cohn is one of our favourite books on Agile User Stories. The book starts with an overview into user stories, and details what a user story is and the different aspects of them. He then discusses how to go about writing a user story, and provides details of the INVEST criteria that can be used to determine if the story is meeting all of its objectives. Next Mike gives an in depth discussion of who user stories are written for and where to begin when gathering the details for them. The book then discusses acceptance testing user stories, including how to go about specifying these criteria and the responsibilities of the development team and customers during this process.
The Agile Frameworks
A 59 Seconds Agile Infographic