Every CCS Project is designed to be Agile from the ground up. Every CCS Project is also designed to fit within a larger set of expectations because we understand that individual projects do not operate within a vacuum.
Every CCS Project is deployed with an online project management interface for both its internal team as well as the client. These interfaces are designed to ensure project transparency and requirements traceability. Our expectation with each CCS Project is to ensure everyone involved is informed, that we remain responsive to client needs and that we achieve tangible, quantifiable progress in making the enterprise more secure.
With our project methodology, we tackle this by developing a Semantic blueprint or foundation. We generally approach this by using preliminary visualization tools (mind map or concept) to illustrate the functional requirements and the relationships between them. Then we designate that as a Domain Taxonomy (or ontology depending on how detailed the relationship information is). The Domain Taxonomy then represents the pool of available terms groups and sub-groups with which to build logically relevant WBS segments. Then we can build requirements taxonomy within my automation environment and extract the WBS from it. Thus we have elements of EA design, semantic correlation and project coordination all wrapped up within one activity. This makes it possible to track project elements from:
- Strategy to EA
- EA to Functional Requirements (the 1st level or elementary taxonomy)
- Functional Requirements to WBS (abstraction of 1st level taxonomy)
- WBS to Technical Requirements (the 2nd level or detailed taxonomy)
- Technical Requirements (precise) to Project Schedules (schedule & detailed requirements taxonomy should map nearly one to one)
- Project Schedules to Roadmaps & What if Alternatives
- and everything back to Strategy
Like programs and operational sustainment, every CCS project has a distinct lifecycle that fits within the larger context.
