Mad Genius’ Agile process relies on user stories to describe requirements. User stories breakdown complex requirements into smaller components that can be completed in a sprint or two. All user stories provide some measureable value to the customer. Mad Genius will help customers refine their requirements into user stories as part of the process.
User stories are estimated using story points. Story point estimation allows the development team and the customer to understand the size of the work involved in completing a given user story relative to other user stories. This is a standard Agile Scrum process that was developed by one of the founders of Agile Scrum, Mike Cohn. An easy way to think of story point estimation is to think of the size of something relative to another. For example, in the world of dogs a Chihuahua is on the small end of the spectrum a Great Dane at the largest end of the spectrum and a Labrador someplace in the middle.
Our Agile development team works closely with you to understand your requirements and deliver high quality software solutions to you. The development team has nn years of experience in the software industry and understands the importance of high quality, maintainable solutions.
Testing of developed solutions is performed within the sprint. No user story is considered complete by the development team until it is fully tested and all known issues are resolved.
5. Documentation and Review
Mad Genius standards require clean coding standards and neatly documented code. In addition to the code documentation, Mad Genius developers provide a documented overview of each completed story for the sprint review.
Have a great Internet idea but don't know where to start?
Madgenius can help you with infrastructure and development resources to get your next great idea off the ground. We can work with any budget to help you succeed. Contact us today for a quote.
Agile Development Methodology
Mad Genius development teams use an Agile Scrum methodology for delivering high quality, complete deliverables to their customers. Development is performed iteratively in small 3 – 4 week sprints. This shortens the cycle for you to review completed work and provide feedback and prioritization of next deliverables for the next iteration. Short iterative development cycles (sprints) allow you flexibility to change your priorities with each sprint. You set priorities and determine when you have enough completed to go live. It’s that simple.