„Alone we can do so little; together we can do so much“ Helen Keller Collaboration is the subject of this post. You will learn about „customer collaboration over contract negotiation“ with considerations for daily use in software development. Collaboration is the keyword. It is hard to imagine software development undertakings that go without contracts. With “customer collaboration over contract negotiation”, all negotiations should happen collaboratively. This means that negotiations are transparent with no hidden agendas. Pricing should be fair for all parties. If a software development undertaking starts with hidden intentions, it will become difficult to work together in a truly agile manner. One of the values of agile software development, trust, is missing from start in this case. This doesn’t mean …

Unfold The Agile Manifesto – Part 1 Read more »

Checking out a shopping cart or shopping cart checkout flow is the process that comes after shopping. This happens when the user is done adding products to his basket. In the checkout phase, a shopping basket filled with items becomes an actual order. This is an essential process in any online shop, since this is when users convert to buyers. With this objective, the checkout process should boost users confidence in the online shop and run smoothly. In this post we won’t focus on the layouts and contents of each page that is part of the checkout flow but on the flow itself. Pages of the checkout flow, for example cart details, will be covered in additional posts that will follow. The checkout process starts after you have added …

Shopping Cart Checkout – What You Need To Know! Read more »

User Stories and their Acceptance Criteria as the base of implementation work is shown by the example of drawing a house in this post.

User Stories are commonly used in context of Agile software development but that’s not a limitation. Acceptance Criteria will allow you to determine whether or not you have completed the implementation of a User Story.

Understanding Agile Story Points or Scrum Story Points seem quiet challenging if you are only experienced with time based estimations. This post hopefully eases the situation and makes Story Points clearer.

Story Points are commonly used in Agile software development. When talking about Agile software development we are talking about Scrum in most cases, but there are other methods as well.

Historically Story Points arise from a military context, when during the Cold War the Delphi Method was developed to forecast the impact of technology on warfare. The goal was to get a forecast or estimation of probability and expected development time of a certain technology in a single indicator.