Agile Banner

We have adopted the best of Agile, that is to iteratively discover an optimal solution to the overall product development, and married it to the reality of working across time zones and in remote locations.

We start with high level architectural representations that evolves into a detailed design for the features and workflows that are most important at that time. One might think of this as rolling wave planning or progressive elaboration. The idea is simple: Plan only what you know, and plan more as you know more.

Net Solutions uses Scrum as its Agile Methodology. Scrum is a simple yet structured framework for continuous delivery, which is primarily focused around a team-based approach to deliver value to the business.

Agile Process Diagram

The Agile Product Backlog in Scrum is a prioritized features list, containing short descriptions of all functionality desired in the product which is collated by Product Owner. The highest priority features are collected into a Release Backlog, from which smaller still Sprint Backlog is created, with each Sprint delivering a working product to the customer, increasing functionality incrementally.

The Backlog is documented following the format of user stories. A client requirement is formatted: As a <WHO>, I want to <WHAT>, so that <WHY>.

  • Bernd Strenitz
    Quote-icon

    We had a great experience with Net Solutions and would readily recommend it to our friends and colleagues who are building start-ups. The team was resilient and worked effectively with our agile/parallel sprints methodology. The programmers were very good, project management was very efficient and QC team was thorough. Our experience with designing was also great.

    Bernd Strenitz

    Founders, at Cheetah LLC

Roles & Responsibilities in a Scrum

Scrum Master

  • Guides the Scrum processes.
  • Looks for ways to fine-tune Scrum.
  • Removes impediments in Sprints.
  • Concentrates on "How to achieve".

Product Owner

  • Focuses on understanding business and market requirements.
  • Prioritizes the work to be done by the engineering team.
  • Works closely with the key stakeholders.
  • Defines the Release and Sprint goals.
  • Concentrates on "What to achieve".

Scrum Team

  • Drives the plan for each sprint.
  • Ensures collaboration towards.
  • Release and Sprint goals.

Scrum Ceremonies

Each of these roles perform "Scrum Ceremonies", a defined set of actions done in an organised, cyclic manner to achieve success for the engagement.

Daily Standup

  • The team meets daily at a scheduled time and meeting is time-boxed to 15-30 mins.
  • Each participant speaks in the below format:
    • What did I achieve yesterday
    • What I want to achieve today
    • What issues are blocking me

Sprint Planning

  • The team discusses the sprint goal and picks user stories that correspond to the goal.
  • It is conducted to plan for upcoming sprints and limited to 2-4 hrs.
  • It is used to plan the velocity of the sprint with reference to the velocity achieved in last sprint(s).

Sprint Retrospective

  • Team discusses the just-concluded sprint
  • Each member should speak 3 things about just ended sprint

Backlog Grooming

  • The team revisits the release backlog to discuss user stories or re-estimate the stories, wherever required.
  • Checks for any RnD areas in the stories.