Warning: Undefined array key "HTTP_REFERER" in /home/unifiedinfotech/htdocs/www.unifiedinfotech.net/wp-content/themes/unifiedinfotech/functions.php on line 377
Agile Software Development Methodology - Unified Infotech

Copyright 2024 Unified Infotech Inc. All rights reserved.

Made with heart in NYC

HOW WE WORK

The process is defined as a sequence of steps. When followed, it helps to achieve a goal. We consider it - the art of thinking through.

Let’s talk about the specifics

OBJECTIVE

  • Run through the entire project with the client based on the initial proposal and agreement.
  • Establish a detailed idea about the goals and business objectives of the client.
  • Understanding the competitive landscape.
  • Understanding the target audience, market & geography
  • Clarifying all queries and doubts which the team has, post initial analysis.
  • Understanding and documenting client’s design and branding preferences
  • Laying down assumptions and constrains!
  • Coming with a high level epic mapping.

OUTCOME

  • Have a precise and clear idea about the client’s and project’s goals
  • Have a clear idea about the likes and dislikes of the client.
  • Getting client’s inputs and clarification on all open-ended points
  • Having all the information required for the planning phase.

TEAM MEMBERS INVOLVED

  • Project Manager
  • Tech Lead
  • IA & UX Lead
  • Project Owner / Client
  • Business Analyst

OBJECTIVE

  • Creation of all relevant documentation required for successful execution of the project
  • Getting confirmation and approval from the client on the documents and materials
  • Defining the project plan
  • Defining the design and branding guidelines of the project

OUTCOME

  • To get everything documented in detail, leaving nothing for chance or assumption
  • To get client’s approval and signoff on the documentation and project plan
  • To have a well-defined and precise planning of the project

DELIVERABLES

  • Detailed technical Specification
  • Wire-frames
  • User Stories
  • Project plan with detailed milestone/sprint planning
  • Test cases and scenarios

TEAM MEMBERS INVOLVED

  • Project Manager
  • Tech Lead
  • IA & UX Lead
  • UI Design Lead
  • Test Lead

OBJECTIVE

  • UI Design of all the project screens based on the approved wire-frames and design guidelines
  • Web, Tablet and Mobile specific designs.
  • Getting system UI Designs approved and confirmed by the client.

DELIVERABLES

  • UI Designs of the projects
  • Clickable prototype on Invision platform -> example link
  • Source files in either Photoshop or Sketch format

TOOLS

TEAM MEMBERS INVOLVED

  • Project Manager
  • IA & UX Lead
  • UI Design Lead
  • UI Designer

OBJECTIVE

  • Catering the requirement for frontend, backend, web services, and API development integration.
  • Prepare a strategy for Agile Scrum methodology
  • Factor the aspects of multi-tenancy, scalability, 3rd party integration
  • To set up a 2-3 week frequency for sprints/milestones
  • Crafting an optimized clean code structure
  • Involve client review in each sprint/milestone

WEB TECHNOLOGIES

  • Back-end. : Laravel, Ruby, Python, Node.JS, Java
  • Front-end. : AngularJS, ReactJS, VueJS Html5, CSS
  • Database. : MongoDB, Mysql, PostgreSQL, Firebase
  • OpenSource : Drupal, Magento, Wordpress

MOBILE TECHNOLOGIES

  • iOS : ObjectiveC, Swift, xCode
  • Android. : Java, Android studio
  • Hybrid. : Ionic, ReactNative

TEAM MEMBERS INVOLVED

  • Project Manager
  • Team Lead
  • Front-End Developers
  • Back-End Developers
  • QA Engineer

Objective

  • Each sprint/milestone is tested manually.
  • Bugs are reported and added to product backlog.
  • Upon bug fixing, quality release is provided and then the final demo of the sprint is sent to the client for approval.
  • Regression testing after each sprint to ensure proper functioning of the previous approved sprints/milestones.

TOOLS

TYPES OF TESTING

  • Unit Testing
  • Manual Testing
  • Regression Testing
  • Security Testing
  • Automation Testing
  • Load & Stress Testing
  • Performance
  • Code Review

TEAM MEMBERS INVOLVED

  • Account Manager
  • Project Manager
  • QA

OBJECTIVE

  • Product enhancement through an Agile approach
  • Regular Security Audits
  • Bi-weekly code back-ups
  • Constant upgradation of the system based on new software/version release
  • Full Testing the system each month to find any bugs, incompatibility and error
  • Monitoring of the traffic and server load and optimizing according to the business needs.

Project Communication Structure

Daily Scrum
Standup

  • Mon -Fri 30 minutes
  • Check previous day’s work, current day’s plans, any queries, hurdles etc
  • Project Manager with the entire Project Team

Weekly
Review

  • Weekly 45-60 minutes
  • "Improvements to process (No finger pointing!)"
  • Client along with the Project Manager & Team Lead

Sprint
Delivery

  • 2-3 weeks 1-2 hours
  • Demonstration for the client.
  • Client along with the Project Manager & Team Lead.

Code
Reviews

  • Bi-Weekly 3-4 hours
  • Code Review
  • Tech Lead

Collaboration Tools

We make sure to use the tools that are top of the market to bring your ideas into reality. Our careful selection of tools makes sure that your ideas are executed with the highest level of efficiency.

Engagement Models

We aim to deliver excellence at every step of projects and finish our job with the top level of efficiency and dedication.

Time and material based

When the scope of your idea is not clear, we tend to go with the T&M based model to provide you with more efficiency as we continue with your project.

Dedicated Teams

To give you control over your project, the dedicated teams will be there at your disposal. We aim to give you a sense of comfort as we work on your idea and our dedicated teams make sure that you do feel that sense of control