Se

A software process model is an approach to the development of software and determines how the project is to be carried out. (phases, activities, roles, methods, tools and documentation)

• Basis for the software project management
• Management: Planning-and control-oriented

A process is the actual execution of sets of (ordered) activities in a projectToday a process model includes looping back to inspect & adapt.

It moves downwards in the project definition phase (Verification)

At the bottom, there's the implementation / coding phase (validation)

After the implemtation, it moves up again with various validation phases (which are corresponding to the phases on the same horizonal level of the project definition phase)

There was a frustation that the traditional models couldn't adapt with the need of fast paced development and changing requirements. Old models caused too much overhead and bureaucracy.

Due to the fast evolvement of the personal computer and the whole industry, developer needed a more flexible approach to get rapid feedback of the endusers.

1. Start where you are
   1. Kanban provides the flexibility to be overlaid on existing structures, without disrupting them. Make changes and extensions as you go.
2. Agree to Pursue Incremental, Evolutionary Change
   1. Kanban encourages continuous small incremental and evolutionary changes to the current process. Don't make sweeping (big) changes, as they usually encounter resistance.
3. Respect the Current Process, Roles & Responsibilities
   1. Kanban recognizes that existing processes, roles, responsibilities, and titles have value and are, generally, worth preserving.
4. Encourage Acts of Leadership at All Levels
   1. This is the newest Kanban principle. It reminds you that some of the best leadership comes from everyday acts of people on the front line of their teams. It is important that everyone fosters a mindset of continuous improvement (Kaizen) in order to reach optimal performance on a team/department/company level. This can’t be a management level activity.

1. Visualize the workflow
   1. The first and most important thing for you is to understand what it takes to get an item from request to a deliverable product.
2. Limit work in progress
   1.  a primary function of Kanban is to ensure a manageable number of active items in progress at any one time.
   2. Limiting WIP means that a pull system is implemented on parts or all of the workflow.
3. Manage Flow
   1. By flow, we mean the movement of work items through the production process.
   2. Ideally, we want fast and smooth flow. This would mean that our system is creating value quickly. This way we can minimize the average cycle time for production and avoiding the cost of delay but in a predictable fashion.
4. Make Process Policies Explicit
   1. You can’t improve something you don’t understand. This is why the process should be clearly defined, published and socialized.
5. Feedback Loops
   1. In order for the positive change to happen, succeed and continue, one more thing needs to be done.
   2. Such are the daily stand up meetings for team synchronization.
   3. There are also the service delivery review, the operations review, and the risk review meeting.
6. Improve Collaboratively (using models & the scientific method)
   1. Shared vision
   2. shared understanding of theories about work, workflow, process, and risk

• CFD (cumulative flow diagrams)
  • to visualize work "in progress"
• Run Chart
• Lead Time Distribution Chart
• Failure Load and Blocker