12/20/2016 Daniel Huchthausen in Methods
Prototypes are a great way to get feedback on design ideas and the feasibility of technical solutions. RAD (Rapid Application Development) is a methodology that focuses on starting development asap instead of writing rigorous design specifications. In contrast to the advice from the first post on software prototyping, to never use a prototype in production, RAD does exactly that. That is why we want to take a closer look at it.
Read more11/04/2016 Daniel Huchthausen in Methods
#NoEstimates is a lean and agile methodology that focuses on the delivery of customer value. To reach this goal it tries to minimize non-value-creating actions like the estimation of implementation effort for User Stories. In the first part we introduced the basic ideas of the methodology. In this part we want to provide some tips on how you can get started with #NoEstimates.
Read more11/04/2016 Daniel Huchthausen in Methods
In the »Lean way of thinking« effort to estimate the implementation time for tasks, user stories or features, is waste, because it doesn´t produce value to the customer, it just makes people feel better. Therefore time spent on such activities should be reduced as much as possible. #NoEstimates is an agile methodology that helps you to focus on creating customer value instead of spending time on things that don´t create value.
Read more10/06/2016 Daniel Huchthausen in Quality
It is already quite common to describe infrastructure in code with e.g. Puppet or Chef. These days there is another option for that: Docker©. Especially for Docker© it is important to keep track of the infrastructure’s configuration, because sources for your containers might have changed or vanished. Therefore you should test your infrastructure to ensure that it is as expected. Serverspec offers you the ability to do exactly that.
Read more09/09/2016 Daniel Huchthausen in Methods
Finding out about all requirements of a product and ensuring their implementation is the key to a happy customer and to satisfied stakeholders. Therefore it is advisable to invest enough time into investigating and finding out about requirements. In the first post about requirements engineering we introduced the "Requirements Traceability Matrix" that allows you to keep track of your requirements. To fill this list with content we now want to take a closer look at possible sources and the classification of requirements.
Read more02/24/2016 Daniel Huchthausen in Technology
SCM-Manager can be connected to several issue tracking applications like Bugzilla, Redmine or JIRA©. The basic functionality of those plugins is all the same: They enable you to change the status and add comments to issues. Beyond that the scm-jira-plugin offers several additional options which we want to explain.
Read more02/24/2016 Daniel Huchthausen in Quality
In the last post we defined quality as » the degree of conformance to explicit or implicit requirements and expectations« and took a closer look at the different terms of the definition. During this examination it became clear that quality starts with thoroughly defined requirments. In this post we want to go one step further and show which steps can be taken to improve quality.
Read more02/24/2016 Daniel Huchthausen in Quality
People often talk about high quality software products, but what is that? How can you measure or compare the quality of an application? Let´s take a closer look at this topic and discuss what quality is all about and how it can be improved.
Read more
