Author: Tassilo Kubitz

Agile Roadmaps in Software Development

| Tassilo Kubitz

Artikel in deutsch ⤴︎

In general, every software solution requires a roadmap, as the basis for targeted further development and so it can be adapted to users’ needs in the coming years. No matter which niche the software serves, it always represents a form of reliable standard for its users. As a result, features are rarely removed, since this is perceived as a loss and impacts user acceptance.

Normally, the product manager is responsible for planning and marketing software. This person is the product-market expert for his or her specific area. The product manager develops a product strategy, known as the roadmap. Software releases are generally implemented in the form of a project, with the help of a project manager. Project and product managers provide each other with significant support by sharing their experiences.

Continue reading →

From solution to problem – advising in project management

| Tassilo Kubitz

Dieser Artikel auf Deutsch

One recurring pattern in software development plays out during the initial phase of the project: The client describes their requirements. So far, so good – everything is clear, and this is also how things are supposed to go. However, it becomes apparent at this stage that the requirements are formulated in such a way that they stipulate a specific approach to arriving at a solution. This method is already familiar, normal, and well rehearsed for the client in this form, so it is more or less viewed as the only way to reach the goal. The thinking behind this is that if only the solution is formulated in sufficient detail, the schedule and costs can be determined directly, and nothing else can go wrong during realization.

Is that really the case?

Continue reading →

Agile fixed price projects – risk or opportunity?

| Tassilo Kubitz

Dieser Artikel auf Deutsch

At first glance, the term “agile fixed price project” sounds like a contradiction in terms. Fixed price projects feature exact specifications, offering both sides clarity as to the services to be performed, the schedule, and the parties’ cooperation obligations. The contractor bears the risk – for which the client pays a commensurate markup in turn in some cases.

The term “agility” means that something is flexible and mobile, so it encompasses change as a characteristic. Agility is becoming increasingly popular, especially in the context of agile software development: Less red tape and more iterative cycles lead to the result that is truly needed at the end of the project.

Changes at a fixed price – how could that possibly turn out well?

Continue reading →