Discovery
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.
-
Unified Infotech process
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
-
UI & UX Lead
-
Project Owner / Client
-
Business Analyst
Planning
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
-
UI & UX Lead
-
Test Lead
Design
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.
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
TOOLS
-
ADOBE XD
-
ADOBE ILLUSTRATOR
-
SKETCH
TEAM MEMBERS INVOLVED
-
Project Manager
-
UI & UX Lead
-
UI Designer
Development
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
TECHNOLOGIES
-
Back-end. : Python, Node.JS, Java
-
Front-end. : AngularJS, ReactJS, VueJS, Html5, CSS
-
Database. : MongoDB, Mysql, PostgreSQL, Oracle, MS SQL,
-
Others. : Apache Ignite, Apache Spark, Pandas, MemCache
-
iOS : ObjectiveC, Swift, xCode
-
Android. : Java, Android studio
-
Hybrid. : Flutter, Ionic, ReactNative
TEAM MEMBERS INVOLVED
-
Project Manager
-
Team Lead
-
Front-End Developers
-
Back-End Developers
-
QA Engineer
Testing
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
-
OATS - Oracle Application Testing Suite
-
JMeter
-
Gattling IO
-
Appium
TYPES OF TESTING/ QA
-
Unit Testing
-
Manual Testing
-
Regression Testing
-
Security Testing
-
Automation Testing
-
Load & Stress Testing
-
Performance
-
Code Review
TEAM MEMBERS INVOLVED
-
Project Manager
-
Team Lead
-
QA Engineer
Maintenance
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
Daily Scrum Standup |
WeeklyReview |
SprintDelivery |
CodeReviews
|
Mon -Fri (30 minutes Check) |
Weekly (45-60 minutes) |
2-3 weeks (1-2 hours) |
Bi-Weekly (3-4 hours) |
previous day’s work, current day’s plans, any queries, hurdles etc |
"Improvements to process (No finger pointing!)" |
Demonstration for the client. |
Code Review |
Project Manager with the entire Project Team |
Client along with the Project Manager & Team Lead |
Client along with the Project Manager & Team Lead. |
Tech Lead |