Agile Pulse Model

Agile Pulse Model - Multi Project Management
Agile Organizations Model – Scaling Agile with Pulse

Principles behind the Agile Pulse Model

Agile Pulse Model – Scaling Agile – is an agile organisational model to manage multi-project businesses (multi-project management) and it is Parmatur´s implementation of lean and agility in companies working with strategy, development and delivery. The aim is to achieve business agility.

Agility is the ability to successfully create, cope with, and exploit changes in circumstances.

It’s all about interaction between individuals, using pulse meetings that create movement and transformation.

Agile Pulse Organizations

Product development – definition

Product development is the transformation of a market opportunity into a product for the customer. The opportunity may have been created by the company itself through analysis, promotions, technology, partnerships or other measures. Or a possibility emerges on the market that the company can use. Product development requires the ability to 1) create business models, 2) establish collaboration with customers, suppliers, distributors and other stakeholders, and 3) develop and nurture products and production systems.

Agile Multi-Project Management
Multi-Project Management

Strategic direction and focus

The portfolio team decide what projects to start and when. Projects are queued and prioritized by the portfolio team. The portfolio team uses daily, or bi-daily pulse meetings for planning, decisions and problem solving.

Business, market and product strategies

Agile Product Development, Multi-Project Management

Strategic teams execute development of business, market and products at a “block” level. Strategic teams use daily pulse meetings for planning, decisions and problem solving. The result is a strategic design.

Resource management

Managing individuals and equipment to prevent overloading.


The work load must be balanced to avoid overloading the R&D operation. This is done in Pulse by using two channels: projects and assignments. Larger tasks are done as projects, smaller as assignments. No line work is permitted.


Project teams use two methods to make sense of project goals and how to achieve them.

Projects use daily pulse meetings for planning, decisions and problem solving.


Assignments are queued and prioritized by the Assignment manager.

Assignments use daily pulse meetings for planning, decisions and problem solving.


All teams meet weekly to coordinate the work and propagate problems.

Creative Commons License
Agile Pulse Model by Parmatur HB is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

Making Organizations Agile