Agile

Agile Software Development was developed by some of the best minds in our industry. Years ago. Since 1998 it has become the way to do things.

Short Iterations
We use 10 day sprints (over two weeks). During each Sprint, we follow a sprint plan. We need two basic sprint plans for the initial sprint for a CMS site or a Development project. These can be patterns, something like:

CMS

  • collect design components from the client using survey page*
  • Create WordPress Instance, connect to domain and email addresses
  • Using a base template* and the core set of plugins* create pages and menus for the Core Items*
  • Liaise with client to collect core information for Contact us and About us page

Development Project

  • Get basic info from the Client
  • Instantiate base site on Cloud
  • Implement User Registration and Auth
  • Client specific steps…

These are not complete! Discussion with the client over Slack is required for 2 – 4 days to flesh out the project.

*there are common elements we can write to make our lives far easier and expand on what we can implement during the first sprint. Each item we develop, we share across the network so that we have constantly rising standards of delivery for that all important first sprint.

TDD (Test Driven Development) – Laravel has an excellent TDD method. Development Projects benefit in quality and speed by using TDD. 100% test coverage is the goal with TDD. It is best practice. If you develop without TDD, then you will spend more time debugging when adding a new feature later.

Sprints – Each ticket on Trello is in a subject column. Each ticket has a label which has a status. These are

Research
Concepts
In DESIGN
ACTIVE
DONE
BUG

When a ticket is done, it stays around until the end of the sprint, and then it is Archived. We do not resurrect a ticket, we create a BUG ticket if the problem arises in a new Sprint or reset the DONE flag if it is not really complete.

Tickets
Each ticket you pick up at the Scrum meeting – you complete that day. Each ticket is given another tag during Sprint Planning which is simply a projection of how many hours the ticket can be done in. This is a planning expectation and helps us organise work. Each ticket is completed with QUALITY first, meaning the deadline is not as important than it is completed professionally and forever. Each Developer has a Label which is used to assign the task.

Example

Scrum
Every day at a strictly appointed time, the team review the Trello board over a Google Hangout. Get your coffee before the meeting, and anyone who does not join the meeting on time will get assigned work. Anyone at the meeting assigns their own work. If work is not completed from the previous Scrum, then it is continued and NO NEW TICKET can be assigned. If it is near the end of the Sprint, other developers may collaborate but most tickets are the singular responsibility of the assigned developer. If you want to claim a share of the reward, then you have to do the work!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.