Skip to Content

FISMA Compliant Hosting

The best software teams ship early and often. Talented teams coupled with customer feedback makes great software! We are equipped with the best agile software development talent anywhere. Our team is well disciplined to plan, track, develop, test and release your software early and bug free.

Our team develops using agile processes specifically Scrum. Our Scrum agile process, emphasizes teamwork, frequent deliveries of working software, close customer collaboration, and the ability to respond quickly to change. Our team is typically composed of:

BEGIN DESCRIPTION OF PRODUCT OWNER IMAGE The product owner image is displayed as a pentagon perimeter with five 
                          sticky notes at each point of the pentagon perimeter. In the center, there 
                          is a silhouette of a person with the caption 'product owner'. There are 
                          five arrows pointing from the product owner to each of the sticky notes. 
                          From the top most and circling around, the notes read: first, 'Has the 
                          vision of where to take the product'; second, 'Brings the team and the stakeholders 
                          together'; three, 'Cares about the users’ needs and knows the business goals'; 
                          four, 'Owns the product on behalf of the organization'; five, 'Responsible for 
                          the products success'. END IMAGE DESCRIPTION.
Product Owner: The product owner's main responsibility is to provide the vision of what they wish to be built. This team member defines the features of the product, the acceptance criteria, and prioritizes the product backlog. They are the customer's lead representative.

Scrum Master: The Scrum Master enables close cooperation across the team and stakeholders and at the same time shields the development team from external interference. This team member coaches the team to their best performance and in doing so, helps improve productivity and remove impediments.
BEGIN DESCRIPTION OF SCRUM MASTER IMAGE The scrum master image is displayed as a rectangular perimeter with four arrows 
                        pointing outwards to each of the corners of the image.  In the center, there is a silhouette 
                        of a person with the caption, ‘scrum master'. The first arrow, which roughly lies at the two o’clock 
                        hour of a watch, goes through a sticky note which reads, ‘Facility Facilitate Change’, and points 
                        to an organization chart depicting the scrum master at the top and the development team underneath, 
                        with the caption, ‘Organization’.  The second arrow, which roughly lies at the four o’clock hour of 
                        a watch, goes through a sticky note which reads, ‘Assist and Coach’,  and points to a group of silhouettes 
                        bunched together; each of a different color with the caption, ‘Development Team’.  The third arrow, which 
                        roughly lies at the seven o’clock hour of a watch, goes through a sticky note which reads, ‘Advise 
                        and Coach’, and points to a single blue silhouette with the caption, ‘Product Owner’.  The fourth and final 
                        arrow, which roughly lies at the nine o’clock hour of a watch, goes through a sticky note which reads, 
                        ‘Explain Agile’, and points to a group of silhouettes bunched together; each of a different color with 
                        the caption, ‘Stakeholders’. END IMAGE DESCRIPTION.

BEGIN DESCRIPTION OF DEVELOPMENT TEAM IMAGE. The development team image is displayed as a triangular perimeter with bi-directional arrows pointing to 
                        each of the development team members which are visually at each corner of the triangle.  At the top of the triangle 
                        there is a blue silhouette depicting the scrum master.  At the right bottom corner of the triangle there is a group 
                        of multi-colored silhouettes depicting the development team and finally, at the bottom left corner of the triangle 
                        there is an orange silhouette depicting the product owner. END IMAGE DESCRIPTION.
Development team: Our Development team is a cross-functional team of developers, graphic designers, content developers, quality assurance, and technical writers. Our Development team works independently and always remains intact for the duration of each Sprint.

Our development cycle is divided into two-to-four week Sprints. Each Sprint cycle contains four types of gatherings: Sprint planning, Sprint review, Sprint retrospective and the Daily Scrum. The product owner will prioritize the user stories to be performed during the sprint cycle from the product backlog. These user stories will be transferred to the Sprint backlog from where the developers will work. At the completion of the Sprint cycle, a Sprint review gathering will take place in which all stakeholders will have the chance to comment on the work done. Any defective user story will be sent back to the product backlog.
BEGIN DESCRIPTION OF AGILE DEVELOPMENT IMAGE. This image is a graphical representation of our agile development process.  In the background, it shows 
                        two half circle, one light green and the other darker green, pointing at each other end-to-end as to form a 
                        complete circle or cycle.  Three labels are depicted and distributed around the circle. The first which 
                        is located at 9 o’clock, contains the caption ‘Sprint Planning’. The second, which is located at one o’clock,  
                        contains the caption ‘Sprint Review'. The third, which is located at seven o’clock, contains the 
                        caption ‘Sprint Retrospective’.  In the foreground, there is a blue streak that depicts the beginning of the 
                        sprint with the caption, ‘Task Breakdown’ and the end of the sprint with the caption, ‘Finished Work’. This 
                        blue streak in the foreground loops about itself in the center of the image and within this inner loop we 
                        can see the caption ‘1-4 week sprint’. Sprouting from the top of the loop, there is a smaller blue 
                        streak that loops around but opposite to the bigger inner loop with the caption ‘Every 24 hours’. END IMAGE DESCRIPTION.

Our sprint cycle will not overwhelm you with endless meetings. Yes, you are invited to all of our meetings, which we call gatherings. We follow the agile process and our gatherings are:

Sprint Planning: The team selects the items from the product backlog that they can commit to completing. From this list, the sprint backlog is created. Also during this time the Team discusses technical requirements for each user story.

Sprint Review: This meeting is designed to collect feedback from all the stakeholders on the Sprint that was just completed. This meeting, which should last no more than 2 hours, exists for the purpose of demoing new features, with an emphasis on test plan compliance and acceptance.

Sprint Retrospective: This meeting is done after every Sprint and is typically about 30 minutes long. This meeting allows us to catch lessons learned and fix issues before they become problems.

Daily Scrum: Short standup meeting, 15-minutes long, tops. The purpose of the Daily Scrum meeting is to find out from every team member:
  1. What they did yesterday
  2. What they are working on today
  3. Whether or not they have any obstacles in their way