DOT1 Solutions Private Limited
Some statistics that can be food for thought for our design team: For every 1 second of delay in page load translates to:
DOT1 provides a quick guide to Quality Assurance leads, Solution Architects, or Project Managers on how they should solution-to-deliver, to ensure quality in Enterprise Content Management projects. The paper propagates that QA is all-encompassing and an integral part of the end-to-end project life-cycle.
Assign a full-time Business Analyst
Project to assign full-time Business Analyst at Project site for the entire duration of the project.
Responsibilities include: Understand Scope of Work (Information Architecture document). Gather business requirements & documenting/updating business blueprint (To-Be document or Functional Specification document). Responsible for walking thru requirements to the development team; and clarifying their queries. Be the conduit between the Business team & development team. Lead all activities with the Business team viz. Conference Room Pilot/ Business Acceptance Test/ User Acceptance Test and End User Training.
Recommended profile for Business Analyst: Overall 10-15 years of work experience. At least 5-7 years in a similar role. Excellent communication skills. Excellent functional knowledge of ECM Products. At least ECM implementation experience. Relevant experience: Website deployment driven by the Sales & Marketing team. Industry/Domain knowledge (e.g. work experience with clients in the private sector/ automobile/automotive industry). Good knowledge of Community and Commerce dimensions of portal solutions. Preferred experience: 2-3 years as Solution Architect (Solution to sell and/or deliver)
Project Key Performance Indicators (KPIs) to be defined at the start of the project to measure success at the project closure. These should be quantifiable/measurable.
Review proposal submitted by implementation partner
The Scope of Work that is understood and documented in the proposal should be reviewed by the IT and Business Team to ensure all stakeholders are aware of what’s in scope and what’s not
The gestation period from the Sales presentation to proposal negotiation & contracting may be high – with the scope being ‘lost’, ‘negotiated out of scope’, delivered as a workaround, or later. It is therefore important for all stakeholders to review the final draft before contracting
Example: Implementation Partner sales team presents slide on Marketing Campaign capabilities with an eye on future roadmap & to demonstrate capabilities of the product suite. These functionalities may catch the imagination of certain stakeholders but may not find a place in the scope of the current project.
Content Verification is unique testing that needs to be conducted by the business team along with or before User Acceptance Test. Content Verification will test or verify that the content that will be published is actually the content that was provided. UAT (User Acceptance Test) will test functionalities and not Content.
Managing digital initiatives: case of Enterprise Content Management
Large ECM projects are usually delivered by teams working out of multiple locations. A project site and offshore delivery centers. In the case of ECM projects, especially for the Development phase, it is important that development items for Back-end processes (transactions) and ‘Look & Feel’ requirements follow a different development cycle. ‘Look & Feel’ requirements are subjective and therefore it would be useful if these are reviewed by business/user teams during the Development phase, instead of waiting till the UAT phase.
Business team to assign a SPOC
Business Team to assign at least 1 representative who is available at the project site full-time during key project phases.
Responsibilities include: Participating in requirements gathering sessions with implementation partner and business to ensure there is no ‘leakage’ of business requirements in terms of understanding or solutioning. Highlight requirements that may need business review, as early as in the development phase. These requirements would largely be in the Look & Feel aspects of the site, which require an iterative process for acceptance. Participate in demo/dry-run/conference room pilot that may be planned by implementation partner. Participate in User Acceptance Test. Be the conduit between Business Team providing timely input and sign-offs to design, content sourcing /verification et al. Attend meetings on need basis for any clarifications et al. Project phases during which this/these representative(s) would be required: Full-time during Requirement Gathering Phase & UAT. Need basis for all other activities mentioned above.
114, Brigade Arcade, Brigade Metropolis, ITPL, 560037
Mahalaxmi Plaza, VC2, Sec-3, Vaishali, Ghaziabad, 201010
29-A, Peace Haven, St. Andrews Road, Bandra (West), Mumbai, 400050