Skip to content

Development Philosophy

BlackCat edited this page Jan 30, 2015 · 17 revisions

Introduction

Starting with 2015 we're going to use a Scrum based development philosophy. Our main plan is to produce more iterations per year to have a better progress instead of having big refactorings and per year releases. Our _Soft-_Scrum helps us to achieve that.

The following rules and statements are oblige with the start of the Sprint 39. Sprint 38 is the start sprint to prepare the base for the future sprints and does not follow all of this statements.

As developer I agree to fulfill the following statements in my development process on CWT

  • BlackCat

Bug-Tickets and User Stories

There will be two types of tickets from now on. Bug tickets and user stories. A bug ticket is ticket that describes a bug that has to be fixed. A user story is an improvement or new feature for the game. Normally a Sprint will be a collection of user stories that has to be realized. This will be called the Sprint Backlog. A new label, InProgress, will be used to mark stories from the backlog as in progress. The code for a ticket will be committed only when all tasks of acceptance criteria are completed. Stories that aren't ready at the sprint end will be shipped to the next sprint.

Sprints

This introduces some new things. The first thing is the Sprint. Normally a sprints is a collection of tasks that will be done in a time window. At the end of the time window you will get a runnable version. This time window is normally from 1 to 4 weeks. As you know CWT is our hobby project and we cannot spend every minute of our lives. Because of that our sprints have a time frame of 3 months. This means we want to release four releases of CWT per year.

In this three months we're going to take two months for developing and one month for testing. After that we release the result.

Clone this wiki locally