The use of agile methodologies is an essential part in delivering quality results to our clients, yet they can be prone to poor documentation practices. Although distinct from a Waterfall methodologies, we know that Agile still requires strong documentation to ensure final product needs are met.
Over the last six years, a 40% increase in the use of Agile has proven its popularity. This enthusiasm is due to both success and tangible results, enforced by means of guidelines. One of these guidelines is the role of documentation. Agile promotes a functional rather than static documentation. At blue-infinity, we ensure that documentation is not an objective in itself, but a tool to help deliver a succesful product and project.
Documentation is the result of the work and not the basis for it. Although Agile recommends face-to-face conversations, it is still useful to create a reliable knowledge base and formalise decisions taken during your project.
Unlike Waterfall, documentation is the result of the work and not the basis for it; only the necessary documentation for the healthy running of the project is created. Minimising documentation allows us to focus on solution design rather than specification, but it must remain relevant as it carries the responsibility of all project stakeholders.
We use wireframes to clearly specify the interactions between users, technology and design.
Development often involves implementing graphical interfaces, which ultimately reflect good product perception and user adoption. It is paramount to clearly specify the interactions between users, technology and design.
To achieve this, blue-infinity’s User Experience team employs a practical and visual approach known as wire-framing, which is the result of having first identified user needs. When complemented with a Style Guide, it permits a fast and easy way for project stakeholders to perceive the interface. Our focus is on the essential: end user interaction.