Back

 

Guideline on defining a process for SpeeDEV

 

Visual Process Designer of SpeeDEV makes it easy to visualize, design and implement development processes both for Requirements and Issues. The schematic of the sample process here illustrates the salient features of the SpeeDEV Process model. The Visio file for the same sample process schematic is available for you to modify to fit your process. This document describes the salient features of the SpeeDEV Process model and the guideline you should follow when you are creating a schematic for your sample process.

 

Salient Features of SpeeDEV Process Model

Roles

The main players in a SpeeDEV process are called the Roles, for example ‘Project Manager’, ‘Developer’, ‘QA Tester’, ‘Customer’, ‘Tech Lead’, ‘Product Manager’ ‘Sponsor’One person (user of SpeeDEV) can be assigned to one or more Roles. Based on hierarchical structure of the project you can even assign more than one person to a single Role. In the Sample Schematic Process the Human Figures designate the Roles. Please note that there are ‘Green’ Roles and the ‘Brown’ Roles. The difference between the Green and Brown are: the Brown Role is a Hard Role as defined by YOU. On the other hand a Green Role is a System Defined Role as anyone can play this Role. For example in the sample schematic a ‘Requirement Proposer’ can be anyone and automatically assigned to the person whoever has created a new Requirement. If you wish to use the same Proposer in your Process use the Green Role and SpeeDEV will know who is the person playing that Role for the particular Requirement.  You can have as many Roles as your process demands with whatever names you wish.

Steps

The Steps divides a long complex process into modular elements with lesser complexity and duration. It also serves the purpose of high-level description of your process. For example your Issue Resolution process may have the Steps: ‘Review’, ‘Development’ and ‘Test’. At any point of time a Requirement or an Issue can belong to exactly one Step. Steps allow you to answer the questions like ‘How many Issues are in the Development Step?’ or ‘What percentage of Requirements are in Review Step?You can have as many Steps as your process demands with whatever names you wish. In the Sample Schematic Process the large Gray rectangles designate the Steps.

Activities

The atomic units in SpeeDEV Process are the Activities. The Activities are nested within a Step and performed by a Role. For example ‘Review’, ‘Implement’, ‘Fix’, ‘Test’…In a Step the Activities can be sequential or parallel and connected to each other by Connection. As part of the Process execution when SpeeDEV comes to an Activity, it creates a Task for the user who is assigned to the particular Role. You can have as many activities of your choice in each step. In the Sample Schematic Process the small Light Gray rectangles with line attached designate the Activities.

Conditional Branching

Very few real-life Processes are simple, linear and sequential. Often the Process follows alternative paths based on different criteria. SpeeDEV allows you to add Conditional Branching both between Steps and between Activities in a Step. The condition can be simple or complex by using AND, OR, NOT and multiple conditional statements. Typically in one or more Activities before the Branching Condition one or more Variables are set by the Roles during the execution of the corresponding Tasks. And the Conditions in the Branching are expressed in terms of those variables. In the Sample Schematic Process the yellow diamond shows the Conditional Branching. The variables used in the Conditional Branching are shown in the Activities with the possible values in italics. You can have two or more branches out of a Conditional Branching based on different criteria.

Guideline for creating a Process for Evaluation

  1. List out all the Roles in your Process. Limit the number of Roles to five.
  2. Make your Evaluation Process with two or at most with three Steps
  3. For each Step list the activities. Limit the number of Activities in each Step to three.
  4. Connect the Activities by Connectors based on the flow of your Process.
  5. Decide if there is any Branching condition between two Steps or Activities. For each Branching Condition determine what variable you need with what values. Then determine in which Activity BEFORE that Branching Condition that Variable value is to be set. The Activity may be even in a different Step than the Branching Condition, but it must chronologically come before the Process reaches the Branching Condition.
  6. Finally end your process by connecting Step(s) to the Red Circle named ‘Stop’.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Back