An Introduction to Agile
A 59 Seconds Agile Training Video
Continue to Next Section Below
Initiating an Agile Project For Developers
A 59 Seconds Agile Article
This article provides a discussion on ‘Initiating an Agile Project’ and looks to discuss what Agile is and the processes involved when starting an Agile project.
Initiating an Agile Project
Let’s wrap up with a summary of what we’ve gone over so far. The amount of unnecessary documentation created in traditional project management builds an obstacle into the product development process. By removing this obstacle by following the agile values and principles, projects are able to deliver value to customers as soon as possible.
Just-in-time documentation ensures stakeholder involvement from the conception of the project, and helps guide the relationship between the scrum team and the stakeholders throughout the entire development process. Only creating the documentation as it is needed clears up the requirements for the scrum team, making sure that everyone is aligned on the project vision. It also reduces the amount of wasted effort and cost in the event that the project has to pivot or is cancelled.
Reduce upfront documentation and planning, establish the team and the communications required with the stakeholders, start developing the product sooner, and deliver the highest value continuously. Development focused on creating documentation only when it is needed allows the maximum amount of value to be produced.
By adopting the agile values and principles, you can reduce the upfront documentation and rigid guidelines that hinder your team’s ability to be flexible and work closely with the stakeholders to create the most valuable product possible.
Initiating an Agile Project:
A 59 Seconds Agile Video Animation
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.
What is Agile?
A 59 Seconds Agile Infographic
Our Favourite Agile Books
We found these books great for finding out more information on Agile Scrum: