A/B TEST

A/B testing is a method where you test two different versions of a feature or product. This is typical on marketing and research. When using this method in software development you have to versions, for example a website. A, could be the existing website (if you have any) and A is typical the control version where…

RETROSPECTIVE

Retrospective is a planed time, usually a meting or workshop where the team can start to reflect over the work that´s been done the last period. Retrospective is where the team can analyse, examine and look for improvements in their work process and also a great way to learn from each other.

WORKING AGREEMENT

Working agreements is a way for teams and organisations to set rules, principles and process between individuals, teams and different decision. The purpose is for the teams to focus on creating value instead of work against each other. So its important to set some ground rules. In the best scenarios teams figure this out by them…

USER STORY

User story is a popular method in agile software development to capture the need of user of a function or feature that are being developed. A User story consist of couple of sentence that describes “Who”, “What” and “Why”. In the requirements process User Storys can be used as a method to define business value…

CODE REVIEW

Code Review “peer review” is technique to examine and review software code, often together with someone else. The intended is to find mistakes and correct bugs early in the development process. With this method you get two more eyes to help you find mistakes in the code. It´s easy to get “blind” for your own…

THEORY OF CONSTRAINTS

Theory of constraints (TOC) is an idea that every system has at least one constraint. With theory of constraints you identified constraints and then try to focus the process and value flow around it. TOC is adopts the idea that “a chain is no stronger than its weakest link”. And only when you increase the…