OUR AGILE
TEAMS
What is an architectural sprint?
In resume it’s the first contact with your project, we will take your idea and turn it into a building plan.
We’ll have answers to these questions:
Why do we want to build it?
What is it? What is not?
How do we build it?
What will we deliver?
We will deliver a manual on how to build the project/MVP, integrated by:
*All documents are accesible using Jira software
-
User Stories
To estimate each story, we will use a T-Shirt size estimation where the greater the size, the greater the risk. Our goal will always be to have as many small size U.S. as possible.
Here an example
-
-
Our Fintech and Blockchain agile teams
MVP team
An small team with experience in Fintech and Blockchain projects that will help you to build your MVP.
MVP+ team
An intermediate team with experience in Fintech and Blockchain projects that will help you to build your product.
Advanced team
A large team with experience in Fintech and Blockchain projects that will help you to build your incremental product.
How do we set up our teams?
With deliveries of our architectural sprint we will have a big picture about project size, and here is where LOE (Level of Effort) do your magic.
LOE for each of our team packages is estimated by pivoting our Small Size user stories since they present the lower risk and therefore are more predictable.
Given that our Small Size U.S. (User Story) is anything that we can do in 3 days or less and requires minimum testing, it has come up with the following pivot:
What will we deliver?
Monthly deliverables in all our plans are the following:
Sprint deliverables are focused to create incremental product for the project
An example could be an overhaul of an existing application:
When an application is being overhauled, data models probably exist. In the first Sprint of the overhaul, we might decide to alter the data models to achieve new results that are desired, this example is an idea about what could be a Sprint deliverable.
Sprint deliverables are monthly recurrence.
For every sprint during the project, stakeholders will have access to real time QA reports, at these, they will see total test cases and your status: Passed, Failed, Blocked and pending.
Here an example
Real Time QA Reports are accessible all time and updated in every sprint.
For every sprint during the project, stakeholders will have access to real time performance metrics, at these, they will see key metrics that will give and detailed status of every sprint.
Real Time performance metrics are accessible all time and updated in every sprint, reports will be accessible using Jira Software.
For every sprint during the project, stakeholders will have access to our sprint report, at this, they will see a consolidated report with detailed status of each sprint.
Here an example
Sprint report is accessible at the end of each sprint.
The sprint demo takes place at the end of the sprint and is attended by the whole Scrum team, including Product Owner and Scrum Master, as well as relevant stakeholders, management and developers from other teams.
The sprint demo is invaluable for keeping stakeholders up to speed with the progress of product development (Incremental product). It allows them to feedback and discuss with the Product Owner and Scrum team any possible amendments to the Product Backlog which would help to maximise value.
Spanish 
English 
