Whether creating a new project from scratch or simply adding to your existing application, a team of 8th Light software crafters and designers can make anything you dream a reality. Years of industry experience has made us the perfect fit to bring your software and application ideas to life.
A fixed budget can be a source of tension on any project, but 8th Light’s unique workflow assures that you will leave with functional software containing only the most important features.
New releases are delivered each week, providing opportunity for feedback to determining the highest priorities. Pay by the feature and not by the hour, and you will know exactly what you are buying. Let our expertise help inform your budget decisions.
We haven’t seen everything, but we’ve certainly built enough systems to be confident in delivering yours. 8th Light has experience in all facets of developing and launching software, and a process by which we break your vision into features that are deliverable within a single week.
You will see a tangible product demoed every seven days so that you may know exactly what your money is being spent on.
Software is incredibly complex, and so is the process of creating it. There will always be uncertainty in any fast-paced environment, but we take the uncertainty out of the software value—you can trust in our expertise, and our ability to deliver.
We will be right there with you, treating your opportunities as our own.
The entire team meets for a half day to understand and establish the value and complexity of the release.
Together we define the smallest set of features needed to deliver value to the business or customer, called the minimum viable product (MVP).
We assign this feature set a ballpark estimate, and develop a budget and date for release. At this stage there is still quite a bit of scope and complexity left to uncover, but it is good to establish preliminary expectations.
Using one or two week iterations, we receive rapid feedback on the existing features, and can then adapt the plan. The best projects treat innovation as a continuous process rather than a moment in time. We can use our experience using the product each week to reimagine what the product could become.
This re-imagination process can even affect the features we decide to develop. We write stories for the following iteration in each Iteration Planning Meeting (IPM). A story is how we translate use cases into requirements that can be built as software. They are made up of a collection of example scenarios required to create the feature, called Acceptance Criteria (AC).
When each scenario in the AC is complete, the story is complete and ready for demo and approval in the next IPM. There are three types of stories that will be part of an iteration, and each will be assigned a “point” value that will be used for billing:
New behavior added to the application.
To calculate story points, we start by estimating the amount of work a story will require in an optimistic scenario, a realistic scenario, and a pessimistic scenario. We combine these numbers into a weighted mean that emphasizes the realistic estimate.
Our final estimate, which is the weighted mean plus two standard deviations, gives us a 95 percent confidence level in our quote. This lets us commit to how much the story will cost.
Upkeep and scaling needed to support an application in the wild.
There is always some amount of unanticipated work needed to deploy and scale an application with users. The team will explain the reason for the additional work, and keep track of the total time spent on the story. A point value isn’t fully calculated until the end of the iteration.
All the iteration planning meetings start with a demonstration of all the stories completed in the previous iteration. The stakeholder reviews the demo, and signs off when a story fulfills all of its acceptance criteria. This sign-off will be used to invoice for the points completed in each iteration.
Research needed to explore how to move forward.
When there is some uncertainty, a little bit of prototyping, researching, or interviewing can save time building. The team will limit the point value in a spike, giving a maximum cost for the story to be completed.