Our Agile Methodology

Agile Development Process at Tech Vedika

  • Tech Vedika follows iterative Agile development approach
  • All projects are divided into multiple sprints,each spanning 2-4 weeks that help in building the product incrementally
  • Sprint Planning: Every sprint starts with a planning meeting involving customer. The team accepts stories from backlog, estimates and commits the target for the iteration
  • Sprint Execution: This is the work the team performs to meet the sprint goal. Every sprint focuses to develop (including detailed design), test and demonstrate the built product
  • Daily standup: This meeting will be conducted with the entire team involving customer (if interested) to discuss following:
    • What was done yesterday
    • What is to be done today
    • Roadblocks (if any)
    • Learning (if any)
  • Sprint Review: The outcome of each sprint will be shared with customer for capturing early feedback
  • Sprint Retro: The sprint retro is a meeting at which the team discusses the just-concluded sprint and determines the changes required that might make the next sprint more productive

Our Scrum Masters

All our teams consist of a Scrum Master whose job is to coach developers and clients to implement best practices in the project.

Our Values


No hiding behind technical language, no surprise delays at the end of projects, no ambiguous expectation setting. Everyone is on the same page and working towards the same goal.


Checking each day to inspect progress towards the sprint’s goal and identify any problems to resolve. At Tech Vedika, we use Red Mine project Mgt Tool that gives everyone the visibility of the progress from anywhere in the world.


Based on this reflection, we tweak and refine the way we are working. We react quickly in order to maximize the impact of improvements. Project changes? We are ready.

What Can I Expect?


The project kicks off with a technical challenge, where a senior developer builds a mini feature. This allows us to anticipate any technical issues before development. Then we sit together at a starter workshop to clarify the business objective of the project and prioritise the features that will help us achieve it .


With a prioritized backlog in hand, we can now plan how to approach the work. Each week, we will spend two hours to clarify the details of each feature with you and then estimating the complexity of this work. This means both you and the developers will have clarity on what to expect.



We work in weekly sprints that focus on the features you have prioritized. A successful sprint is one where every item identified in this week’s backlog is done. Once we have built the minimum set of features, we go into auto deployment mode and release as each new feature is built.


We check ourselves against burn-down charts which map time against the amount of work we anticipated to complete. This means no tunnel vision – if there’s a problem, we will solve it before the end of day. We will also send a concise daily email with an update on the work done that day.


The development team has a daily stand up to ensure they are a strong team as possible. Moreover, we dedicate some time each week to take stock, review the next week’s work and retrospect on how we can tigen the process further.