Services

Our Clients

• American Express Publishing
• BIC
• Bide-A-Wee
• Campbell Soup Company
• Catapult Marketing
• Circle One
• Creative Good
• Dairy Management, Inc.
• Dannon
• FocusVision Worldwide
• FontHaus
• Grey Global Group
• Media.com
• Pedigree
• Pica9
• Ryan Partnership
• Squidoo/Seth Godin
• Technology Pathways

Better software, faster!

Overview
Brainloaf is an Agile Software Developer. We follow the Scrum development process. Below is a flow chart of the process.

Process
Development is performed in interations called sprints. The following things happen during each sprint:

1. The Product Owner Define Features
2. The Product Owner Chooses the most critical features according to business needs
3. Developers develop those features and automate testing
4. Working software is delivered

Roles
A small number of focused roles are important to the Agile process.

First, the Product Owner. This user is responsible for defining new features to be implemented and must be a stakeholder in the application itself. They represent the interests of the end users and the customer organization.

Second, the Technical Lead is responsible for managing the flow of development within the Agile process. They are responsible for running the sprint planning, daily standup, and sprint reviews.

The team members are the developers who will be implementing the desired functions. They are software developers, QA experts, designers and subject matter experts.

Sprint Planning Meeting
At this meeting, developers will estimate the highest priority features from the feature list. A feature must be a concise and small. They typically are 4-12 hours in duration. If a feature is too large, then is should be broken down. Based on the task estimates, the team will determine how many features can be implemented within this sprint. Only these features will be implemented during the sprint. The Product Owner must approve this list at the planning meeting. This list of features is locked at the conclusion of the meeting and cannot be modified.

Daily Meeting
Everyday the Technical Lead will run a daily meeting with the team. The meeting will last exactly 15 minutes and must get started on time. Each team member will discuss what they have accomplished since the last meeting, what they will accomplish next and what barriers to progress they have encountered. The Technical Lead will address the barriers after the meeting.