Initiating an Agile Project
A 59 Seconds Agile Training Video
Continue to Part 3 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
There was a lot of upfront effort developing the documentation for your project, which eventually translated into a great expense. You and your team spent a lot of long meetings hammering out every point of the customer’s requirements and committing to a specific interpretation of those requirements. The documentation that your team spent so long on, made it difficult for you to actually work on developing the product; instead, you were spending your time creating paperwork.
Now that you’ve realized you didn’t build the product that your customer wanted, your hands are tied due to the contractual requirements within the documentation that were laid out before you started developing. Your team has come up with easier, quicker and more valuable ways that they could deliver the requirements, but they don’t have the flexibility to accommodate these ideas within the contract your company signed with the customer.
To change the scope of the project now in order to make the product that the customer actually wants would make a lot of the existing documentation invalid, meaning a large amount of the work that went into developing the documentation is wasted. This reworking of documentation will push the project over budget, demoralizing the development team and creating friction between them and the customers.
The amount of documentation required in a traditional development project can create extra constraints on the development team, forcing them in a direction that could be inefficient and waste time and resources. If you only create the documentation you need NOW for the project, then you can start to develop the product much earlier.
Continue Reading —> Next
Initiating an Agile Project:
A 59 Seconds Agile Video Animation
Continue Reading —> Next
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.
Continue Reading —> Next
What is Agile?
A 59 Seconds Agile Infographic
Continue Reading —> Next
Agile Scrum Master Training Course
Our Favourite Agile Books
We found these books great for finding out more information on Agile Scrum:
Continue Reading —> Next
