 |
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
 |
|
|
|
| | |
|
 |
Consulting |
|
|
Our consulting service begins before your first consultation:
Together we define a path to the solution. |
|
|
Establishing a (tool-based or even non-tool-based) system development process requires a consistently planned, step-by-step strategy. Each phase is defined with consideration to the overall solution. And yet each phase needs to achieve a previously defined result. This is how jointly defined milestones come about. These milestones are tied to in the evaluations and decisions on objectives and requirements in the later stages of the process. The initial deciding factors are the requirements and company-specific methods which are focused entirely on you.
At the beginning there is an analysis.
What needs to be more efficient in the future? This must be analyzed with regards to your current processes (phase 1):
- Analysis of current development processes in the diagnosis: actual practice vs. documented processes
- Interviews with employees involved
- Actual vs. plan comparison using analysis and documentation of the actual practice (basic activities/best practices)
- Identification of medium-term competency fields using the V model
- Definition of requirements for future processes, activities and roles
- Definition of interfaces between requirements and test management
Results: Documentation of the status quo; requirements for a medium-term process vis-à-vis the defined objectives. Time required for this phase approx. 2-3 months.
This is followed by process definition.
Based on the requirements derived in the previous phase, we then develop the future process definition:
- Draft process (requirements, development, implementation, testing)
- Process model (phases, people/roles, tools, objects/documents)
Results: Documentation of the future development process; proposal for using the development tools; proposal for practice with development objects and their links. Time required for this phase approx. 3-6 months.
This phase results in a role concept and a project plan.
Involvements and responsibilities are defined with regards to the process previously defined:
- Grouping of activities
- Interface with project planning
- Interface and methods for quality assurance
- Other strategic planning (activity portfolio, resource planning, controlling and milestones)
Result: The project plan.
The documentation, review and final presentation complete phase 1.
Phase 2 builds on the results obtained in phase 1. As per the project plan, the following are offered as part of pilot projects:
- Workshops
- Training
- Coaching
- Customizing of development tools
Furthermore we develop a handbook, specifically for your development process.
You will see:
Our consulting service does not have to end after the consultation. It all depends on the maturity of the development processes that have been implemented in your company. We will be happy to continue offering you support, so that in future you are able to answer as many software engineering questions as possible, using your own knowledge base.
|
|
|
|
|
| | |
|
|