Project Management/Feature Driven Planning

First Step
Middle Step
Last Step

CLEVER CIRCUITS GmbH

OUR PROJECT PLANNING IS

Dynamic & Flexible
Our Team is young and dynamic enough to handle new or updated requirements. We know this issue management as Feature driven process.
Real & Feasible
Our Plan is daily updated and synchronized to the real working progress.
Transparent
Our customer and suppliers can follow up our Planning from their desktop and see the progress and any occurred changes.
Poor on resource usage
We optimize continuously our work to that energy and resource which is needed to achieve our work and not more.
Continious learn curve
Our weekly team meetings give us the opportunity to exchange our experience permanently during the project and take a "lesson learned" to the next tasks.
Involves competencies from 360 Degrees
Our Team Leader evaluates the competencies of our Team and Teams from Suppliers and give the planned tasks to the right members. In this way we can reach the best work results in the shortest time.
Customer Requests Negotiation & analysis
Our Product Owner are responsible for maximizing the value of the customer requests. They analyse and negotiate them with the customer.

Our Product Owner are managing the Product Backlog of the project with their clearly expressing user stories. They are ordering the user stories in the Product Backlog to best achieve goals and missions.

They are optimizing the value of the work the Development Team performs.

They are ensuring that the Product Backlog is visible, transparent, clear to all, and shows what our Scrum team will work on next.

They are ensuring our Development Team understands the user stories in the Product Backlog to the level needed.
Stakeholder Requirements Handling
Our Systems Engineers are branching the Requests of our customer to Stakeholder Requirements and are categorizing these to Systems Requirements which are software, Firmware, Hardware or mechanical Requirements.

Our Systems Engineers are building the product releases with the defined features (Group of Systems Requirements) and schedule them to defined increments (sprints) fixed by our product owner and our customer.

At this stage our product prototypes are born.
Beginning with the prototyping
After creating our Product Backlog, we select the user stories responsible for building our first Prototype and schedule them in the first Sprint.

Our Sprints contain and consist of the Sprint Planning, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective.

We make regularly backlog Refinement.

We give our Product Owner and our Development Team time to do decomposition, review/refinement of backlog user stories and estimates.
Testing our prototype
We test our prototype deeply before deliver it to our customer.

Out Test procedure consists of multiple test scenarios.

During our software Testers are accomplishing Unit Tests, our hardware engineers test their designed hardware.

At the end we do our system tests consists of the whole system which is to defined by our customer.
Prototype approval with our customer
We make with our Customer together system test.

Our customer defines the system by itself and we make a system integration and validation of our product inside the customer's system.