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