Examples of Task Breakdown

Planning Tasks throughout the Project

The following tables show possible tasks within a CQ5 project. For each phase, the main actions are listed; within these possible tasks and/or issues to be considered. These lists are meant as quick-reference, they do not (cannot) offer a 100% comprehensive list of all possible tasks, but are meant to act as a springboard. The list of tasks will vary with each project.

You can make your initial estimates of time and effort for (high-level) task definitions; these should include an indication of to who (customer or partner) will do what and when.

Detailed planning can then relate available or required resources to deadlines and costs.

Note

Certain of the comment fields show the example proportions used to calculate effort when there is a direct relationship between tasks.

Examples of Task breakdown - Concept and Planning

Action  Details / Issues to be considered / Comments Effort Estimation
Kick-off Workshop
Project Concept
Ensure that the Corporate Identity is available and clearly defined.
Architecture Concepts (Hardware / Software / System configuration)
Required system availability
Clusters
Disaster recovery
Centralized data storage
Classification of data, and any access requirements
Integration in a secure server landscape
Target Metrics (e.g. visitors, hits, data volume, etc)
LDAP failover
Buffer to cover growth forecast
Organizational responsibilities
Platform / Browser requirements
CRX Connectors
Feasibility Analysis
If necessary and requested by the customer, a feasibility study and/or prototype can be made.
Project Handbook (with specification)
Clearly define the role of anyone involved in the project; including steering committees, project teams, development teams, support contact, etc.
Define any specific processes and/or tools to be used during the project. For example, customer specific processes, bug and feature tracking tools, etc.
Official acceptance sign-off by both customer and project team is recommended.
Project Planning
Scheduling of regular (intermediate) releases for customer testing and assessment.
Schedule tasks according to resources available. Consider which tasks can be performed in parallel, any independencies between tasks, resource availability and the experience level required to actually perform the task.
Make time / effort estimations; these can be fine-tuned as the project progresses.
Hardware requirements
Plan the soft and hard launches to cater for performance monitoring and training.
Total Concepts and Planning

Examples of Task breakdown - Technical Specification and Design

Action  Details / Issues to be considered / Comments Effort Estimation
Detailed Requirement Specification


Help the customer define their requirements in the form of Use cases.

Define any conventions used; e.g. naming, structure, programming guidelines.

Define any exclusions being made.
  Indicate the Copyright, Licenses and Disclaimers.
 

Define the detailed requirement and functional specifications, covering all aspects of the project (including other tasks listed in this table) and clearly highlighting what has been requested, and what will be delivered.

Official acceptance sign-off by both customer and project team is recommended for this document / document set.
Total Technical Specification and Design

Examples of Task breakdown - Development

Action  Details / Issues to be considered / Comments Effort Estimation
Globals
Setup of the Global Framework and Development Environment
Design parameters and settings
Structural preparation (location of components, templates, etc)
Components

Standard components (e.g. Richtext, Image, Column Control, List, Download, etc). See the Default ComponentsUser Guide for a list of all standard components.

Customer specific components (e.g. Contact paragraph, RSS-feed, eCards, navigation, etc)

A rough estimation of 2 - 4 hours for each component atom will cover all development requirements. This can only be used for an initial estimate, an experienced CQ5 developer should make the detailed analysis.

Templates
Templates for the landing page and main content page types (average circa 5)
Other standard functionality
LDAP / Active Directory connections / Single Sign On
Portal Integration
Closed User Groups
Backup / Versioning
HTML Integration
JavaDoc documentation
Notifications
Multi-language capabilities
Workflows
Linkchecker
Web statistics
Content Importer (Word, XML, etc)
Media Library / CQDAM
Web Access requirements (see also http://www.w3.org/WAI/ )
Customer specific functionality
OSGi services
Migration Tools
Subtotal Development
Developer Testing / QA 15% of Development
Follow-up / clarification during development 10% of Development
Documentation 15% of Development
JavaDoc Documentation 10% of Development
Support of customer development team
Total Development

Examples of Task breakdown - Testing

Action  Details / Issues to be considered / Comments Effort Estimation
Functional Testing (customer)
A Test Plan should be documented detailing test cases, each scenario, expected and achieved results.
Performance Testing
Initial performance tests can be made on the test environment. These must be repeated during deployment, then integrated into ongoing monitoring processes.
Bug-fixing 15% of Development
Total Testing

Examples of Task breakdown - Content Generation and/or Migration

Action  Details / Issues to be considered / Comments Effort Estimation
Analysis
Preparation and Tests

See Post-deployment Tasks.

Total Content Migration

Examples of Task breakdown - Deployment

Action  Details / Issues to be considered / Comments Effort Estimation
Installation - Development Environment
Installation - Development Tools
Installation - Test Environment
Installation - Production Environment
Installation - Web-server / Dispatcher
Configuration (with initial Monitoring)
System parameters
User authorization
Total Deployment

Examples of Task breakdown - Post-deployment

Action  Details / Issues to be considered / Comments Effort Estimation
Performance Tuning
(Basic) Performance testing, analysis and tuning
Content Population / Migration
Automatic content load (e.g. from Word into CQ5)

See

Launch Support
Assistance during launch period, and at the switch-over
Total Post-Deployment

Examples of Task breakdown - Training

Action  Details / Issues to be considered / Comments Effort Estimation
Preparation of training material
Workshops
Total Training

Examples of Task breakdown - Acceptance Tests and Sign-off

Action  Details / Issues to be considered / Comments Effort Estimation
Define (and agree) on acceptance test cases
Define when / how often the acceptance tests will occur; for example, on a regular basis, for each milestone, or only at project end?
Define exactly what constitutes success and failure for each individual test case.
Perform the Acceptance Tests
Total Acceptance Tests and Sign-off

Examples of Task breakdown - Project Management

Action  Details / Issues to be considered / Comments Effort Estimation
Ongoing Project Management and Governance
20% of project costs
Communication and Meetings
Regular Project Reporting and status reports
Controlling - time and budget
Legal
Ensure that all legal definitions have been clearly communicated and acknowledged by the respective party. These may cover liability issues through to access requirements for disabled visitors.
License acquirement
Risk Management
Change Management
Handover to Maintenance Mode
Total Project Management

Examples of Task breakdown - Summary

After each individual category has been analyzed you can formulate the final summary:

Action  Details / Issues to be considered / Comments Effort Estimation
Subtotal
...Any customer specific costs or discounts...
Total
VAT
TOTAL