How Does the Development of the Solution Play Out
A quick guide to how software development projects run
How does the solution play out?
If you are taking the Agile route, you’ll find yourself relying on teamwork, collaboration, time-boxed tasks and being flexible to change throughout the solution build. If you are working to a traditional, ‘waterfall’ approach there’ll be an emphasis on linear processes, documentation, upfront planning and pressure on budget and timeline.
A high proportion of software builds now work to Agile management, this is our preferred and recommended approach. You’ve chosen your development team so how does the magic happen?
Be ready to be highly involved right from the start and the whole way through. You will need to help create the user stories, i.e. an informal, general explanation of a software feature written from the perspective of the end-user and participate in regular review calls.
Your product build won’t follow the linear route of creating all the functionality, test and debug, it will be split into multiple iterations. Comprehensive testing will be happening early doors and throughout the build as opposed to being saved up until the end.
The build will evolve and, at the end of each iteration, you’ll have a working end product that has a subset of functionalities of the final product.
If problems crop up, it won’t be down to one person to fix it, it’ll be all of you, you included. Remember, it’s about the product and the requirements can change throughout development to ensure the optimum solution is created.
There will be reviews of the product build after each iteration and again, you’ll be part of the team. The reviews are your chance to check on progress and ensure the solution is everything you had imagined and more. If things have gone off track or aren’t as you’d imagined them, these regular reviews help to quickly steer things back in the right direction. You’ll have more than played your part and will have been part of a team successfully pulling together in the creation of a viable product.
A typical Agile development project follows this path:
Gather initial requirements from stakeholders
Capture vision for the product
Plan out development work
Create user stories for work
High-level estimate of user stories
Build is broken down into iterations (known as Sprints)
Work for each Sprint is agreed upon and clarified before it starts
All functionality created during the sprint must be tested
Product is demoed to stakeholders at the end of every Sprint
Stakeholders have the opportunity to provide feedback
Feedback and changes can be incorporated into the next Sprint
Regular reviews help to shape the vision of the product
At the end of each Sprint the product can be delivered
Products can be delivered over multiple iterations
High priority or core features are delivered first
Additional functionality is added over time