What is Agile Scrum and what role do the developers play within an Agile Scrum projects? This article takes a look into what is Agile Scrum.
What is Agile Development?
A 59 Seconds Agile Video Animation
What is Agile Development for Developers – Part 2
A 59 Seconds Agile Article
In Agile software development, less is more. The Scrum team only documents what is absolutely necessary. As a result, the total amount of paperwork is more manageable. Not only that, requirements come directly from the stakeholders. Team members collaborate with stakeholders to create user stories. This generates requirements that represent valuable features. Plus, stakeholders can clearly communicate what they want from the product.
What is Agile Scrum: Requirements
With better requirements and documentation, developers have a better idea of what they are creating. They aren’t pigeonholed into writing code in one particular way. As long as they create software that satisfies the needs of the stakeholders, the feature makes it into production. Since the inspect and adapt process allows the team to improve their methods, each sprint should produce requirements a little more effectively.
What is Agile Scrum: More Obvious Results
Perhaps the most overlooked benefit of Agile for developers is seeing the results of their work. In Waterfall development, developers may never see the fruits of their labor. Many projects go years before official release, and some never get released at all. Developers that sink time and effort into these projects would certainly like to see their creation be put to use. Having a project die before it goes to the public would devastate the morale of any developer on the project.
In Agile software development, this is almost never the case. Once a project starts, it almost always gets released to customers. Not only is it more likely to get released, the iterative nature of Agile means releases go out more quickly. For any given feature, a developer’s code will be in the hands of customers in weeks. Developers can rest assured that they are not working on something that will never show off their abilities.
What is Agile Scrum: Value
With an Agile project, developers spend more time working on valuable features. They end up with less wasted work, and the entire team works toward methods that work best for that particular team. It may be an adjustment for developers coming from Waterfall software development, but the benefits of Agile are entirely worth it.
Prev <— Continue Reading —> Next
Learn More: An Introduction to Agile
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.
Prev <— Continue Reading —> Next
Learn More: An Introduction to Agile
What is Agile Scrum?
A 59 Seconds Agile Infographic
Prev <— Continue Reading —> Next
Learn More: An Introduction to Agile
Prev <— Continue Reading —> Next
Our Favourite Agile Books
We found these books great for finding out more information on Agile Scrum: