The Project Manager and a appointed person at CLIENT will provide project management throughout the course of the project. The three guiding principals that govern project management are:
- Control – always being in control, understanding where we are in relation to budget, schedule and scope and how they all relate to each other.
- Transparency – we’re in this together and there is nothing that goes on behind closed doors or in a box. We are working together as collaborators.
- Communication – open and honest communication throughout the project, communication is both formal and informal. An agreed upon rhythm of communications will be established and Project Status Reports will be provided routinely.
Project Status Reports
Crimson Agility provides Project Status Reports to our clients weekly or bi-weekly depending on the level of activity. The Project Status Report is relevant, timely, and insightful. The following details are addressed in each Project Status Report:
- Executive Summary
- Update on Budget, Schedule and Scope
- Budget consumed to-date and for the period covered
- Accomplishments for the period covered
- Plans for the next period
- Risks Identified and Mitigation Plans
- Open Issues
- Invoice Summary
The Project Status Report is sent to the project sponsor and project leader for review and sign-off. Any disputes or concerns are always addressed as soon as identified.
During the project, when we identify elements of significant complexity it may be determined that a more formal design document may be required. This documentation will be prepared through collaboration with our client on requirements and agreed upon at completion.
Some examples of elements requiring design documentation are complex workflows, business rules, and integrations with external systems. Our blueprint for building these elements is based on the design document that is derived from discussions, decisions, and the refinement of the design. A good design document will include, but is not limited to the following:
- The fields being captured in the module or interpreted for decision support logic
- Data mapping and transformation rules from one system to another if required in the case of integration or data migration
- Key use cases and the planned procedure for each use case if logic is being introduced which deviates from out of the box Magento functionality
- Key metrics and dimensions expected for reports that are to be built based on data or fields being added
- Business logic for workflows including the trigger conditions, actions, and alerts
- Executed user interface behaviors for any custom feature or functionality
The design documents will be reviewed with users or internal stakeholders to create a written design of the final solution for their sign-off.