How to Inject More Energy in Your Next Retrospective
Are your retrospective meetings boring and time-consuming? When you first adopt agile methodologies, the impact of retrospectives is huge. You can almost see the electricity in the air when people...
View ArticleClik here to view.
What Can Testers Learn From the Vasa Incident?
What on Earth does a 17th-century Swedish warship have to do with agile software project management? For those of you who aren’t familiar with this classic case study of project management gone wrong,...
View ArticleClik here to view.
Writing Requirements for Your App
For a software delivery company, as soon as the idea for a new application is conceived or presented to the team by a client, the next step involves mapping out all the components of the final...
View Article8 Must-Know Testing Tips for Mobile App Developers
Apps developed nowadays have to be launched in a marketplace that’s never been as varied and dynamic as it is presently. The startling diversity in situations and environments that your app can be...
View ArticleHow To Manage Technical Dependencies
Ulf has written about technical debt before, saying that essentially, poor planning and bad implementation of system changes will increase technical debt. Basically, technical debt is work that will...
View ArticleManaging Dependencies – What Else Should You Think About?
So what should your plan to manage technical debt and dependencies look like? You might think at first: let’s always upgrade all dependencies to the latest version as soon as possible! This way we...
View ArticleHow to measure the efficiency of testing
As software products become more complex, the pressure on testers to deliver products free from bugs has risen to higher and higher levels. Unfortunately, limited resources, tight schedules and...
View ArticleTaking Behavior Driven Development (BDD) for a spin: What it is and how to...
Behavior Driven Development (BDD) is a software development process that emerged from as a shift in the thinking and practices associated with TDD (Test Driven Development) and ATDD (Acceptance Test...
View ArticleWhy Agile Trumps Traditional Software Development
Traditional Software Development Traditional software development is conducted in distinct stages or phases, each with a definite beginning and ending. A typical breakdown of the different stages...
View ArticleRequirements in Agile Software Development
The Goal of Agile Methodology To develop a functional product with all the basic requirements in place. When working agile, you must think in terms of: working on width instead of working at depth....
View ArticleClik here to view.
Scrum: An Agile Introduction
One of the most common agile models in use today is Scrum. Description of the work flow in Scrum: Product Backlog. This is the list of requirements to be implemented at some point. The requirements...
View ArticleChoosing Your Scrum Team Size and Structure
Composition of a Scrum team A Scrum team normally consists of about 7 people or, to be more precise, 7±2 persons, so ideally no fewer than five team members and no more than nine per team. All...
View ArticleGiving Constructive Feedback in a Scrum Team
Since open communication is critical for a Scrum team to function smoothly, it is vital that you set up effective systems for when and how you give constructive feedback to the team members. This is...
View ArticleCreating a Product Vision and Roadmap
Product vision describes the product’s goals and customer value. It relates to the problem that the product solves. A vision supports a product-oriented mind-set which increases clarity by creating a...
View ArticleWriting a Vision Statement with the Elevator Pitch Technique
The elevator pitch is a way to articulate the vision so that it can handle the classic elevator test, i.e., can you explain the product’s vision of a person in less than two minutes (before the...
View ArticleHow to Build Your Product Backlog
The product backlog is always based on the roadmap. The backlog contains requirements that are sufficiently detailed and traceable. The requirements must be prioritized so that the most important...
View ArticleClik here to view.
Using User Stories to Document Requirements
User stories are a way to describe the requirements at a level of detail that fits perfectly in a sprint backlog, but also in the Product Backlog. When it comes to requirements for the next 1-3...
View ArticleRelease and sprint planning
Choosing requirements from the roadmap to a sprint It is the product owner who chooses requirements from the roadmap, refines them and moves them to the product backlog. The choice is made based on...
View ArticleClik here to view.
Creating a Product Release Plan That Actually Works
A release plan details the development of a specific feature from beginning to end in a series of sprints. A release can consist of anything from one to multiple sprints. It is be the product owner...
View ArticleSprint Demos vs Retrospectives – What’s the Difference Between the Two?
Sprint Demos The purpose of a sprint demo is to showcase what has become clear in the sprint. The team’s role is to demonstrate to the Product Owner this fact. Product Owner role is to check whether...
View Article