Home - Nerdy Dragon Web Development - Design, SEO, and Software Innovation

Sprint Based Development
We believe the most efficient, effective, and best method to develop projects is using agile development methodologies. We use a variant of SCRUM, where development is broken down into release cycles, or “sprints”. Each sprint is conducted over a 1-4 week period, for optimal efficiency; however we are flexible with setting the duration of the sprint.

Prior to starting a sprint, we look at the list of tasks that we’d like to accomplish, estimate units for each, select a set of tasks that fall within our allocated budget (sprint backlog), and progress accordingly.

Each day, we update the status of our tasks “assigned”, “completed”, “impediment” and track the number of “completed” units that we have for the sprint. This measurement is part of our “daily burndown chart” where we track how many units we’ve completed of our total and how effective we are as we progress through the sprint.

We have 4 sprint options available, which are detailed above. We also work under custom arrangements, including entrepreneurial and innovative agreements.

What are units?
When estimating tasks, we assign a unit value to each task - keeping in mind the number of hours necessary to complete the task. The units we choose from are: 0,1,2,4,8,16,32 (some companies use fibinaci, we’ve chosen this set) When tackling a project, we break the project into tasks that fall within the scope of these units.

How does is a sprint conducted?
Product Owner: First things first, the client assigns a “product owner”, a business representative that is in command of the business requirements and value of the sprint. They’ll be our point-of-contact when we have questions or are in need. They’ll also provide brief, consistent participation throughout the course of the sprint.

Sprint Planning: We begin with a sprint planning session. We take a look at all of our requirements/features/things that we’d like to accomplish (Product Backlog), and choose our top priorities to select a sprint from.

Sprint Backlog: Once we have a solid list, we’ll dig in and break down the sprint into individual tasks assigning a unit value to each task. Based upon our sprint scope, we’ll select a set of tasks that fall within range; creating our “Sprint Backlog”.

Sprint Progression: We’ll kick-off the sprint, and begin progressing against the tasks. We conduct brief daily (or bi-daily) status meetings. At these meetings, we answer 3 questions:

1. What has been worked on since the last update?
2. What will be worked on until the next update?
3. What impediments, if any, are there?

We keep these meetings to no longer than 15 minutes, and do not require the product owner participate, although an open invitation is extended.

Sprint Review: After the sprint is completed, we review what we did, what we did well, what we can do better, and any other matters that will be beneficial to future success.

We offer development and SEO focused sprints. SEO focused sprints will produce the following:

1. Quality in-bound links
2. Improved product titles, descriptions, and product information
3. Quality supplemental content to promote products and increase page rank
4. Improved analytics capabilities
5. Brainstorming and Innovation with SEO strategy
6. Test campaigns to validate/invalidate innovative concepts