Agile Development

Agile development approaches product development with an intent to deliver the product with incremental and regular delivery of functionality to the customer. This enables a functional product to be deployed within minimum time. This way we can collect customer feedback earlier and correct any requirement mismatch if necessary.

Hire Tech Team uses agile management tools like Azure DevOps and JIRA for managing product development lifecycle

Sprint planning, execution, and tasks management

  • Sprint planning is a primary event as to what can be accomplished in each sprint and how.

  • The product owner defines sprint goal and backlog items.

  • A sprint predetermines completion time estimate and project is broken down into activities for execution.

  • The scrum Master, development team, product owner choose best possible approach to achieve sprint targets. Each Sprint lasts for two weeks.

  • Sprint planning sessions are motivating and create a productive environment for the team. The entire scrum team participates in this exercise.

Product backlog and User story creation

  • The product backlog, a one source of truth, is a list of new features, enhancements, bugs, application changes, which team delivers to achieve project milestones.

  • It consists of work items like Epics/Features/User stories, Tasks and Bugs.

  • User stories represent a unit of functionality that completes an end-end user flow.

GIT repositories for source code hosting and control

  • Azure DevOps provides GIT repository for storing application source code. Version control features are used to check in and checkout code.

  • Code reviews happen during each commit in the form of a pull request wherein developers review code as per best standard practices set.

  • Code is merged with application code after it clears quality checks.

  • Test cases and test plans creation and execution in line with acceptance criteria.

Test Cases

  • The QA team writes test cases to validate if implemented features meet software requirements and function as per acceptance criteria.

  • Also ensure system meets all application standards, guidelines, and end user requirements.

  • Test Steps, test data and pre/post conditions all included in test case document verifying requirements.

  • The test cases are executed in an automated way with continuous integration and continuous delivery (CI/CD) pipeline.

  • Automatic test case execution results in business improvement.

Test Plans

  • A Test Plan outlines test strategy, objectives, timelines and resources required for project execution.

  • Tests are conducted to ensure proper software functioning, with tests managers in charge.

  • The Test Plan evolves with the project and always remains current.

  • It is the single source of truth from which a QA team's testing activities are carried out and coordinated.

  • Test Plan acts as a reference for Business Analysts, Project Managers, Development Teams.

Defect fixing and triaging

  • The QA team tracks application bugs and defines bug queries.

  • With queries, they can manage and list active, unassigned, unresolved bugs and their trends.

  • The queries and query charts can be added to your team dashboards to monitor bug status and progress.

CI/CD Pipelines and automated deployments

  • The Azure CI/CD pipeline aims at Continuous Integration and Continuous Delivery to build and test code and ship a highly-performant and quality product.

  • These pipelines can be defined either by UI of Azure DevOps or using YAML files.

  • Continuous Integration generates deployable code, and other artifacts to be deployed.

  • Continuous Delivery deploys the built code into different environments like Development, UAT and Production.

Project burndown and velocity charts

  • In addition to sprint burndown chart, teams can review the velocity at which they work sprint over sprint.

  • The velocity chart tacks backlog items worked-on in a sprint.

  • The burndown chart is a tool which helps manage a sprint.

  • The chart provides comparison of actual progress over sprint plan estimation. The team velocity can be utilized as input into the forecast to help manage your sprints.