The quarterly publication of the International Legal Technology Association
Issue link: https://epubs.iltanet.org/i/67910
lessons learned Live Meeting. We were also mindful that if handled correctly, we could use the time zone differential to our advantage — allowing development to take place during Sydney business hours and review during London's business day, we had the potential to keep the project moving 16 hours a day. In early 2011, we moved into the commercial negotiation phase (working on the basis of time and materials in the early scope and analysis phases to a fixed fee for the various stages of build). While the commercial side was being locked down, we were lining up our internal project team, bringing together our specialists from KM, IT and business development to lead the project. Our team, based in London and Hong Kong, brought together a useful mix of skills. By March 2011, we were in good shape to get started. Contracts with the vendor were signed, licensing discussions with Sitecore were underway, we were exploring options for a managed infrastructure and we had locked in a high-level timeline for analysis and prototyping to commence onsite in London in April. Rapid Prototyping To Elicit Requirements Eliciting business and functional requirements is often a difficult task. Upon arrival in London, our lead from BlueArc spent time with each of our key stakeholders, learning about the current solution and what we wanted to achieve in a new one. Instead of translating these requirements into a written document, they were turned into a series of wireframe prototypes that were used to map out key functional requirements, allowing the team to visualize how the site would be assembled. The wireframe prototype carried no graphic design but provided us with: • The overall sitemap • High-level navigation • Page layouts (including page elements) • Various user journeys and how they would operate through the site Proceeding to elicit requirements through rapid prototyping/ wireframing was incredibly valuable. risky metadata is flying out of your firm 130 Peer to Peer