Startups Frequently Asked Questions

What is your approach to help start-ups?

Letzgro has condensed rich experience of working with startups across the globe.

Working with startups has its specifics:

  • agile approach;
  • focusing on MVP;
  • interrelation of product and marketing.
 

Do you require detailed technical specification?

We can’t overstate how important it is to have specification nailed before development process starts. Efficiency of time-to-market and budget are the main purposes to have each part of the project specified in as many details as possible.

That said, we do not require the specification to be given to us. We can collaborate together to create specifications, and the only condition for this, as well as for project’s success, is your ability to be involved and provide your time to discovery sessions, SCRUM procedures and out-of-SCRUM activities.

 

Have you worked with many start-ups?

Yes. Technological companies at startup phase have been our major clientele.

Do you advise us to write all specs out at once and have a big delivery?

Some of the most successful projects we participated in were due to serious elaboration on concept stage.
We suggest that we work on specifications for an MVP scope of the product.

 

What tactics do you advise to keep good view on progress? (Daily iteration/ deployment to test environment?)

SCRUM methodology will ensure you are on pulse of things:

  1. Daily standup meetings.
  2. Weekly:
    1. sprint planning;
    2. sprint demo;
    3. sprint retrospective;
  3. Story points assigned to every user-story by the SCRUM team that helps understand the scope.
  4. Burndown chart that helps understand the estimated time of delivery.
 

What is your delivery process?

Environments

Before development commences, we set up separate environments:

  1. development sandboxes – place for developers to experiment with their code integrate it and do initial testing;
  2. QA environment – place for QA team to do full formal testing;
  3. staging environment – place for a release candidate that successfully passed the testing and is pending integration into production environment;
  4. production environment – public environment accessed by users.

Repository

We use git-based bitbucket as decentralized code repository.
Here is how we make the most out of Bitbucket:

  • access to code with client;
  • smart commits & JIRA integration;
  • branched development;
  • pull requests and code review.

Continuous Integration

We use continuous integration tools to manage deliveries.
Jenkins is our choice, and we have configured it to support:

  • Code Style compliance;
  • code optimality level;
  • unit tests coverage.
 

How do you suggest optimizing testing time?

We strongly suggest implementing approaches of TDD and BDD, which means that code will be accompanied with tests that will be developed before the actual coding starts.
They will help:

  • double check the integrity of scope;
  • define criteria for acceptance;
  • automate acceptance;
  • automate regression testing.
 

Who is testing on your end? (The development team or independent testers)

QA Team at Letzgro is a separate department. Once QA specialist is assigned to the project, they collaborate with Project managers, Customers, and Team Members to establish the standards for quality, define test plans and develop test cases.

 

What issues have you encountered in the different phases with remote work?

Remote work by itself is not an issue. It is usually a set of specific mistakes that project stakeholders and participants make that disable future success.

Speaking about remote teams, cultural fit is the main requirement. People need to have similar understanding of what satisfaction, quality, optimality of process is.
Main issue at initiation stage is lack of introduction into business goals, plans, dependencies and specifics, that may influence project team members in the future either directly (they will not deliver up to some expectation because the expectation was assumed but never expressed), or indirectly (lack of motivation, connection to business goals and important deadlines).