How we work

Know more about who we are

Making a decision to do something this is the first step. We all know that nothing moves until someone makes a decision.

We follow Scrum Software Development model

Scrum is a powerful framework for managing medium to complex software projects.

01
Objective, Idea

Understand and analyse the project objective or product idea. Analyse the target market/audience and study competitors and their offerings. Understand functional and non-functional requirements. Identify potential risks and challenges. Do SWOT analysis. Planning of the resources required (time, money, personnel). Set timelines and milestone.

Artifacts: Request for proposal (RFP), BRD includes business, functional and non-functional requirements. Capture Epics and user stories, User Acceptance Criteria and may also develop Prototypes / Mock ups / Wireframes as needed.

Roles: Stake Holders, Product Owner, Scrum Master.

02
Planning, Ramp up, Design

Brainstorm, Sketching, mind mapping, and collaborative workshops and Work closely with developers to bring the design to life. Deliver different types of Architecture. Develop UX, Wireframes, design principles, best practices, test plan.

Artifacts: System Architecture, Security Architecture, Infrastructure Architecture. Sprint backlog, UX and wire frame artifacts and more.

Roles: Stake Holders, Product Owner, Scrum Master, Architect as part of scrum, Scrum (Development) Team

03
Sprints, Development, Testing, Release

We follow weekly or two weekly sprints based on the clients needs. Backlogs are assigned to scrum development team. Developed code is reviewed, unit, integration, functional tested. Not all sprints will result in release of the changes. Release Managers precisely design the release strategy, outlining the scope, timeframe, and quality criteria for the impending upgrade

Artifacts: Software code, reviews, Code analysis, Test scripts, Test Data, Test results, Signoff.

Roles: Stake Holders, Product Owner, Scrum Master, Architect as part of scrum, Scrum (Development) Team

04
Pilot, Go-Live

Define the scope of the Pilot or Go-Live. Setup the production environment. Conduct Pilot/Pre-production testing. User training and onboarding. Risk mitigation strategy. Bug fixing and production performance monitoring.

Artifacts: User guidelines, support guidelines, Risk mitigation document, user signoff.

Roles: Stake Holders, Product Owner, Scrum Master, Scrum (Development) Team

Tell us about your idea, and we’ll make it happen.

Let’s Get Started

Careers

There’s always room for intelligent people who are excited about the digital world and are continually looking forward to seeing what’s next.

View Positions

Our Values

Our values mold the way we work with our clients, delivering excellent solutions supported by cutting-edge technologies

Know more

About us

Figcube established in 2018 and has been offering world-class technology solutions to our Global Clients.

Know more
up