PRODUCT DEVELOPMENT

Having years of hands-on experience in project and solution delivery combined with extensive expertise in banking, insurance and retail industries, Intellica’s team is capable to successfully deliver sophisticated projects using modern products and proven technologies. Intellica’s project delivery option is focused on data management and analytics domains, implementing solutions for a variety of clients on the market, which are about to monetize their data and improve decision-making processes

Typically, our projects consist of the following phases:

• Business analysis and requirements
• Business case feasibility analysis
• Design and technology justification
• Delivery
• Maintenance

Presence of mature software development expertise enables additional value to be provided to clients, e.g. customization, software development, integration.

Specification, Prototyping & MVP Development

Specification and Prototyping are the best practices and first steps for developing ideas into initial version of product or service

Specification

Specification is a process of shaping ideas into structured, executable, verifiable written form. Often specification process comprises initial idea feasibility and reality checks.

Intellica Specification services are:

• Workshop (1-3 days focused work)
• Specification via remote collaboration (t&m, usually 40-100 hours)

Specification: Workshop

Workshop is a 1 to 3 day session between you, Intellica Proxy Product Owner or Project Manager and potential team members. It is performed to ensure and facilitate knowledge sharing and discussions around the idea of a product or service.

Why Workshop?

• Helping developers understand business requirements and priorities is essential.
• Workshop allows transforming ideas into specs and tasks, eliminating uncertainty during the development process.
• Proxy product owner or project manager with your business domain understanding will join you on the workshop ensuring that ideas are structured and shaped in best possible way.
• Professionally facilitated communication and brainstorm. Our consultants will facilitate discussions during workshop.
• Efficient Transition – Both you and your future Proxy Product Owner or Project Manager are present, ensuring an efficient transition from ideas to specs.
• Accurate Scope – A workshop will give both you and your potential team a complete accurate understanding of the project’s scope
• Shared Goal – Get sparring, review and ensure that everyone is on the same page

Objectives:

• Knowledge sharing and structuring
• Common vision between stakeholders
• Meeting with potential team
• Excluding disruptive late-stage changes in project concepts
• Identifying best practice implementation areas

Workshop can be conducted on Client or Intellica premises. It is recommended to conduct at Intellicas premises

Deliverables:

• Requirements specification
• Top-level system overview, interaction flows, integrations, APIs
• Assumptions and risks
• Project estimation
• Commercial offer, if applicable

Participants:

• You or your business representative
• Workshop facilitator and/or Intellica Proxy Product Owner or Project Manager
• 1-2 members of potential team (optional)

Specification: via remote collaboration

Objectives:

• same as a workshop, excluding meetings
• Knowledge sharing and structuring
• Common vision between stakeholders
• Excluding disruptive late-stage changes in project concepts
• Identifying best practice implementation areas

Deliverables:

• Requirements specification
• Top-level system overview, interaction flows, integrations, APIs
• Assumptions and risks
• Project estimation
• Commercial offer, if applicable

Participants:

• You or your business representative
• Workshop facilitator and/or Intellica Proxy Product Owner or Project Manager
• 1-2 members of a potential team (optional)

Prototyping

Prototyping is the activity of creating prototypes of software applications, i.e., incomplete versions of the software program being developed, usually in order to retrieve feedback.

Intellica Prototyping services are:

• UX Prototyping (wireframes, mockups)
• Functional prototyping

UX Prototyping

During the user experience (UX) prototyping, the UX consultant will review the idea and/or the specification and come up with:

• information architecture design,
• user interface ideas,
• workflows All of the above will be implemented in the form of UX prototypes.

UX consultants can provide you with a range of UX prototypes:

• Simple solution mockups (main 2-10 screens)
• Wireframes with transitions, validation, logic, and activities description
• Clickable solutions prototypes (wireframes) • Clickable solutions prototypes with finished UI

BUSINESS ANALYSIS

WEEK 1 DISCOVERY

• Introduction
• Review business processes and understand business needs.
• Interviews with stakeholders, documentation study, contextual research
• Definition of use-cases

WEEK 2 FUNCTIONAL & TECH ANALYSIS

• Working on the feature list
• Prioritization of the features
• Definition of MVP
• Technical assumptions
• High-level architecture
• Recommended technology stacks
• Hosting approach (cloud/on-premise)

WEEK 3 PROJECT PLAN

• Project Plan
• Project approach
• Timelines – combined in a high-level project plan (i.e. how many sprints we will have, key milestones, etc.)
• Team and resource plan (weekly FTE plan)
• Budget – estimation
• Project risks

Business Analysis Workshop Deliverables

USE-CASES

Use-case is a representation of a user journey through the product.

FEATURE SET

Prioritized list of features. We turn product expectations into actionable, detailed deliverables.

MVP DEFINITION

We spend a lot of time gathering all of the project features and requirements. We then prioritize the core part of the feature set for the 1st release.

SOW

The scope of work contains a detailed description of the work process and deliverables.

TECHNICAL APPROACH

• Technical assumptions – Platforms, code base, OS needs, end-user devices, etc
• High-level architecture – Custom created solution diagrams
• Recommended technology stacks
• Hosting approach (cloud/on-premise)

PROJECT PLAN

• Project management approach
• Timelines – how many sprints we will have, key milestones, etc.
• Team and resource plan (weekly FTE plan)
• Budget – estimation
• Project risks

PROJECT MANAGEMENT

Project Plan describes the general vision of implementation flow. It shows the main project phases as a sequence through a timeline. Phases can go in a parallel as well as consistently. Project plan provides a clear vision for that.

Rough efforts estimation report is done on the initial stage of the project and contains the assumptions and prognosis for the development phase.

Detailed efforts estimation report with a breakdown structure by module and features is done after completion of BA phase and a clear vision of the app’s structure and requirements.

Throughout the course of the project, all efforts are being tracked and reported through the task management system (Atlassian Jira)

Any time the project stakeholders are capable to check the status of the current sprint/task and the corresponding amount of hours spent by team members.

Using a Kanban approach in Intellica all the stakeholders can track the progress within the active sprint.

Process: SCRUM

Scrum is an agile way to manage a project, usually software development. In the agile Scrum world, instead of providing complete, detailed descriptions of how everything is to be done on a project, much of it is left up to the Scrum software development team. This is because the team will know best how to solve the problem they are presented.

This is why in Scrum development, for example, a sprint planning meeting is described in terms of the desired outcome (a commitment to a set of features to be developed in the next sprint) instead of a set of Entry criteria, Task definitions, Validation criteria, Exit criteria and so on, as would be provided in most methodologies.

Scrum relies on a self-organizing, cross-functional team. The scrum team is self-organizing in that there is no overall team leader who decides which person will do which task or how a problem will be solved. Those are issues that are decided by the team as a whole.

And in Scrum, a team is cross-functional, meaning everyone is needed to take a feature from idea to implementation.