Discovery and Definition start with the requirements specification. This step is called Discovery. This critical step clearly documents the client business processes to be automated by the new software system. These requirements ultimately become the expression of work to be performed and are typically managed closely. Significant change to requirements is avoided. When the requirements are fully vetted, the project moves to Design.

Discovery and Definition Activities

Typical Discovery activities include but are not limited to:

• Knowledge transfer of process requirements from client
• Define data migration scenarios
• Define data integration scenarios
• Define supporting infrastructure - important if meaningful integrations are necessary or the system will be hosted internally
• Project charter definition (larger projects)
• Project structure and phasing (initial findings)
• Success definition

This is great! We have the project framed in. What's next? Read More