Case study: CL3VER
Understanding visual designers and architects needs was key point as a start. That helped to identify major tasks and common problems to solve. Next exercise to do was unification. At the end, Cl3ver is composed by an ecosystem of products that interact with each other. So keeping consistency along all those interactions was vital to reduce frustration and product learning curve.
Collaboration, online edition, projects management, sharing experiences, exporting visuals, and many more features were added to Cl3ver’s core. Work process was completely iterative: analyze, design, prototype, test and build. Two different teams of developer participated in the entire project and everything was handle using agile methodologies.
SCOPE OF WORK