“By failing to prepare, you are preparing to fail.”

— Benjamin Franklin

Discovery and request analysis

Discovery: requirements elicitation

It all begins with the Discovery Phase. We initiate an intensive, one to two weeks, discovery sprint organized to help our team grasp the core components of the business, gain industry specific knowledge, and most importantly understand your technical requirements precisely and completely. Here you work with your PYTEX Business Analyst, Project Manager and a dedicated Software Architect. At some point within this phase, we add the UI expert, UX expert, and your future Lead developer to attend discovery workshops, but all team members can be included as well, if the project requires full involvement of all team members from early discovery sessions.

The deliverables of this phase are properly formatted SCRUM user stories and journeys, which we document in Pivotal Tracker or Jira, or any other project management system of your choice. Based on these deliverables, we develop wireframes, UI/UX creative concepts, and any other creative documentation necessary at this phase.

user stories

We help you write solid user stories and user journeys of your future product, in proper SCRUM format, to ensure your functionality is easily described to the rest of the team members for best collaboration.

User stories

User Story Format:

As a [role] I want to [task] so that [goal].

User Story Example:

As a visitor-user I want to be able to post videos so I can share them with friends and friends of friends.

Backlog

Backlog

Once we have the backlog of user stories, the team estimates the complexity of each user story. Here the Product Owner and the Team define user story details: goal, process, expectations, description, acceptance criteria, etc.

Backlog estimation

User Story Estimation

The team collectively estimates complexity of each user story and divides the stories amongst each other.

Sprint planning

Sprint planning

Before every sprint, a Sprint Planning Meeting (SPM) is held. Here, the Product Owner prioritizes by importance all User Stories previously defined and estimated in the Backlog Refinement meetings. Based on their previous experience and estimated effort for each user story, the team agrees on the number of user stories that they can commit to completing in each sprint.

Sprint:
repeat X times

The proper SCRUM process is executed in a number of iterations called Sprints. Each sprint is started by a Sprint Planning Meeting (SPM) in order to determine a sprint backlog - a list of the tasks to be performed during the sprint, and specific goals to be attained by the end of the sprint.

Daily meeting

Daily stand-up meeting

We start every morning with an internal stand-up meeting to assess the progress. The meetings take no longer than 15 minutes, all members come prepared with the updates and every member is asked the following questions:

  • What have you accomplished yesterday to achieve the goal?
  • What is your plan for today?
  • Are there any roadblocks that could jeopardise the deliverable?

If an issue is identified, before it grows into a problem it is collectively solved without disturbing the process.

Sprint review

Sprint review

Inspect and improve the product.

This is the time for the team to demonstrate the work done within the iteration, get immediate feedback from project stakeholders and the Product Owner, and celebrate the team's accomplishments.

Sprint retrospective

Sprint retrospective

Here we inspect and improve the process.

During the Sprint Assessment (SA) meeting, the team has an opportunity to openly express their thoughts on the sprint cycle. We discuss what went well and what can be improved in the following sprint. The things we learn during the Sprint Assessment meeting provide valuable information for continuous optimization of our processes.

Shippable deliverable:

Product increment

Every sprint must deliver a usable and shippable product component, even as a basic first iteration.

Responsive screens

Responsive all-around

Everything we build for the web is responsive in nature and adapts to screen resolutions, browsers, and operating systems. We go even further. Every project we build has an API component (usually node.js API) which makes app development a breeze.

Got a cool project?

Let us help you build and launch it.

Fill out a questionnaire to get started