“Almost-Scrum” or what is also known more generally speaking as the Avalanche Model is not a good project approach to find yourself in with your development team. On Wiki you’ll find the following description: “The Avalanche model is a Software Engineering project management anti-pattern, it is a combination of a sequential process such as the […]
5 reasons why embedded device development projects fail
Missing stakeholder support “The project is defined, so implement it and roll it out” does not work well in human organizations. Every entity and person has its own target, purpose and agenda. That is the way the world works, so one must take into account the process (and the time) it takes to get all […]
The energy harvester is ready for iteration 3
Iteration 2 overview Wind power to dump load switching has been the main topic of iteration 2. In our system design we also call this Power Management Decision 1 (PMD1). PMD1 should realize several system requirements and, because we have an energy harvester model in Enterprise Architect, this list of requirements can easily be generated […]
The energy harvester is ready for iteration 2
Iteration 1 overview Iteration 1 was mainly about extending our software platform which we call Simple Platform Abstraction. This platform enables us to easily experiment with new hardware (sensors, mosfets etc.) and will be the fundament of our energy harvester application. See the pictures for some recent hardware hacking! The software platform evolved quite a bit. We […]
4 really good things about Scrum
Here are my 4 favorite scrum-activities: Sprint Planning meetings Daily scrums Retrospectives The backlog Sprint Planning meetings Planning meetings are at the beginning of each sprint. During these meetings the team looks at the most urgent user stories, then breaks them down in tasks, and then estimates the time it will take to implement each […]
The energy harvester is ready for iteration 1
Iteration 0 overview A few months passed since the start of our energy harvester project and, given our limited project time, we’re making a steady progress. Implementing a new product in a new domain introduces technological uncertainties, and therefor, we proposed a top-down, bottom-up development approach which is part of an iterative engineering process. At […]
Adopting MISRA-C guidelines in your software development process – best practices
Implementing functional safety by means of achieving a certain safety integrity level (SIL) is a matter of reducing risks. On the software side this results among other things in the adoption of a language subset, which often is a required SIL parameter. As C and, to a lesser extent, C++ are popular programming languages for developing embedded software, a […]
Development: a mixed top-down, bottom-up approach
Introduction In a previous post we proposed our RTOS engineering process: a lean and iterative process, which cycles between project management and development (see Figure). In this post we describe our development approach that can mitigate the risks and uncertainties of developing a new product in a new domain. But before we come to that, we introduce the two […]
The engineering process
Introduction Let us begin with a recap. The goal of this blog is to describe how we develop: a new product in a new domain, with a short time-to-market, and given a minimal budget. Although our product – the “energy harvester” – is only used for illustration purposes, it is well chosen because building it, […]
Recent Comments