An Introduction to Agile
A 59 Seconds Agile Training Video
Continue to Part 9 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
Once the project vision is decided and translated into the product backlog, the team has to make sure that they don’t stray from the goals of the project. Throughout the project, your team holds joint application design sessions, or JAD sessions. These are open to the stakeholders so that they can help the development team clarify the specifications of the product. If the users are involved in the entire project through these JAD sessions, customer satisfaction will be higher when the product is finished.
As each sprint is completed, a sprint review meeting is held. The team also executes SWOT analysis, where SWOT stands for strengths, weaknesses, opportunities, and threats. Which helps them foresee things that may potentially derail the project or create obstacles. The team identifies the strengths, or the advantages the company has over their competitors; they identify the weaknesses, which are the areas that need improvement; they identify the opportunities, or the trends and market gaps that the company can take advantage of; and they identify the threats, or the external factors that might threaten the company or product.
Once these factors are defined, the team will be able to perform a GAP analysis. This is a comparison between the actual performance of the project and the potential performance. This helps the company improve for future projects.
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
