Contents

1. Offer creation.

1.1.       Kickoff.

1.2.       Features definition.

1.3.       Signoff.

1.4.       Create a financial offer.

2. Software development process.

2.1.       Establish the product team.

2.2.       Software Development using agile methodologies.

2.3.       The agile software development process.

2.4.       Release & Maintenance.

2.5.       Details about the work on a Feature.

2.6.       Team structure.

3. Examples.

1. Offer creation

1.1. Kickoff

Goals

1.Identify the project owner

2.Identify the stakeholders

3.Gather input from all stakeholders

4.Define the business needs

5.Define success factors (KPI)

6.Define the expectations

7.Define the non functional requirements

Participants:

  • Project owner
  • Stakeholders
  • Solution Architect, Business Consultant

Output:

  • User requirements
  • Processes, Mind maps

1.2. Features definition

 

Goals

1.Create official project scope

2.Convert user requirements in product features

3.Create an application architecture

4.Create an application design

5.Define the non functional features

Participants

  • Solution Architect, Business Consultant

Output

  • Product Requirements document which will be presented to customer for signoff

1.3. Signoff

Goals

1.A meeting with the project owner is organized

2.Stakeholders are welcome, but optional (can be informed offline)

3.The architecture, design and feature set is explained

4.Feedback is gathered in order to be incorporated

5.Final version is created and handed over to customer for final signoff

Participants

  • Solution Architect, Business Consultant
  • Project owner
  • Stakeholders (can be informed offline)

Output

– Updated product requirements document

1.4. Create a financial offer

 

Goals

1.Discuss with the developers the feature set

2.Calculate for each feature best- and worst-case scenarios

3.Create an offer

Participants

  • Business consultant
  • Development manager

Output

  • Product Requirements document which will be presented to customer for signoff

2. Software development process

2.1. Establish the product team

– Agile software development processes are used

  • 1 Iteration equals to 2 weeks of work
  • The project owner (the Customer) defines a Product Owner (PO)
  • The Supplier defines a dedicated Project Manager (PjM)
  • A certain number of developers are assigned to the project

scrum-artefacts

2.2. Software Development using agile methodologies

An iteration has three artifacts:

1.Iteration planning – the work for the next two weeks is defined

2.Demo of the work done in the iteration, with the PO, PjM and evtl. Stakeholders

3.Iteration retrospective: what went well, what didn’t

-Software Development and testing is happening between

-The content of the iteration can’t change during the iteration

Advantages:

– Full visibility on the project’s progress

– Maximum flexibility in setting the priorities

– Direct contact with the development team during Iteration Planning and Demo

2.3. The agile software development process

scrj

2.4. Release & Maintenance

By using Agile software development methodologies, we ensure that there is always a functional application.

If the feature set available at a certain moment is chosen carefully, the application can be released.

For mobile Apps (iOS, Android) we ensure the publication and approval in the respective App Store.

After release, during the maintenance period, we monitor application’s performance using.

  • various KPIs built in the application
  • user feedback in the App store

We take full responsibility for the availability of the application:

  • Perform bug fixing
  • Perform releases of the fixes

scrum-details1

scrum-details2

2.5. Details about the work on a Feature

– Split the Feature in User Stories

-Define non functional requirements

  • User stories
  • Define technical requirements (give story points, etc)
  • Split the US in tasks for the team members
  • Development
  • Testing Integration in the existing project
  • Demo
  • Documentation of the U.S.
  • Security testing of the feature
  • System testing of the feature
  • Documentation of the feature
  • Beta testing preparations (if needed)
  • Incorporate beta testing feedback (if needed)
  • Create/Update Marketing materials
  • Training of Sales Engineers
  • Training of Support Engineers
  • Product release

Note: a feature can be implemented in one or more iterations, depending on the complexity

2.6. Team structure

– It depends on the type of features requested

– Available resources:

  • Senior SWD
  • Tester
  • Project Mgr
  • Business Consultant
  • Security Architect
  • Solution Architect
  • Marketing
  • Documentation

Note: all SW Engineers perform also testing of their work. The tester performs mostly integration and system testing

3. Examples

For more details about the type of projects we create, please see the examples below: