TrueScrum -

Instincts

, Experience and

User Driven

.

Our TrueScrum methodology means you can realize your vision for building web applications faster and in a more iterative manner. It’s a simple process that we developed and it has proven to be an effective means for web application development, especially when requirements are not clear. But it takes experience, good instincts and user centered discipline to pull it off. We have all three.

We determine the basic scope and agree upon a fixed price for a 30-day sprint. Sprints are a specified period of time where we deliver as much functionality as possible. TrueSrum gives you complete control over how much you want to include in the development process with your application. Fixed pricing for each sprint makes development predictable and extremely flexible.

Call us at 919-228-6310 and lets TrueSrum your next project.

Here is how a TrueScrum 30-Day sprint works:

The First 5 Sprint Days:

  • Define the application. We prepare a brief overview of what the application is, its purpose and who will interact with it. We note any integration or data needs as well as any specific technology requirements.
  • We develop a functional inventory. Think of this as a laundry list or wish list of all the functionality that would be required for this application. We don’t need to define this in any great detail. We just want to document the list of functionality. We can categorize for you based on some logical grouping of components later.
  • Prioritize our functional inventory. Now we have our list of desired functions and we need to go through a process of prioritizing the functionality and identify our highest priority items.
  • Build user stories. User stories are just that. We select a few typical users and build scenarios or stories around how they will interact with the application. How will they start? What will they do? What are they looking to accomplish. What do they see? What are their outputs? Basically we answer whatever questions are necessary to complete the users story. It does not have to be perfect but does have to give us a solid understanding of user interaction.
  • Lock it down. We need to agree upon steps 1 – 4 and then hand off to our development teams. You provide any design assets of direction as well so we can incorporate into our work.

The Next 20 Sprint Days

  • We go away into development seclusion so to speak. We take all of the input and allow our development team complete focus on development and delivery with as much functionality and capability as possible. Generally, we are not as concerned with design but we can incorporate any visual design elements as directed or agreed upon.
  • We are iterating ourselves with our internal teams with a goal to have a working prototype at the end of the sprint.

The Last 5 Sprint Days

  • We share our work with you. We QA what we have together. We document what we like, what we don’t like. We determine best course for the application moving forward – what works and what works better.
  • You have a working prototype (level of functionality varies depending on application). You can make go/no go decisions. Or, better yet, we can decide what needs to be done for the next sprint or how many more sprints we may think are necessary.
  • Start another sprint. We revise our functional inventory and priorities, refine our user stories and build a better application.

Call 919-228-6310 or email us today about how we can put TrueScrum to work for your business.