Our way of working

Yes, surely we do practice real agile, but in our vision the way to a ultimate celebration needs a few steps. The project starting framework model to successful project will surely help to accomplish this

Demand Assessment

Define demand

• Define the need for and benefits of the new development

• Create & share artifacts like current system documentation, mockups and requirement documents.

• Share artifacts with OutSystems Centre of Excellence (CoE)


• Discuss internally whether OutSystems is fit for purpose for this requirement

• Organize Skype meeting with business and OutSystems Centre of Excellence

• Debrief on artifacts and requirements

• Discuss expectations

• Explain agile way of working and the different roles and responsibilities

• Determine initial high level ballpark and feasibility

Design, scope & size


• Organize one or more sessions to understand the application and requested features

• Based on high level demonstration or explanation of features and/or process

• Understand what to build from a user perspective as opposed to technical how

• Design the application based on personas: who is doing what

• Capture User Stories with sufficient level to determine high level scope and related sizing

• Determine initial delivery expectations: Demo, Proof of Concept (PoC) or Minimal Viable Product (MVP)

Scope & Sizing

• Determine scope and sizing for product development (Demo, PoC, MVP)

• Determine prerequisites and challenges for build and implementation (integration with other systems, # stakeholders, involved BUs, availability of business and test data, dependency on other systems’ deployment calendars)

• Create estimates on #sprints, timelines and cost (CoE & Development Team)

Step 3 - Decision

• Discuss scope sizing and feasibility

• Decide whether sizing and costs are acceptable

• Align and allocate on budget



• Create Scrum team: Assign Product Owner, Scrum Master, Business (sponsors), Development Team

• Ensure Scrum-Agile project approach and ways of working is understood; educate if needed

• Determine project logistics, tools and next steps


• Plan meetings: Daily scrum, Sprint Planning, Sprint Review/Demo, Sprint Retrospective

• Create product backlog

• Plan Sprint 0-1 backlog


Agile-Scrum product development

• Incremental development of Sprint Backlog items

• Refinement of user stories

• Delivery of usable product increments

• Maintenance and (re)prioritizing of the Product Backlog

• Monitoring and adjusting long term expectations and release plans

• Decide whether to continue development



• Implement in organization; create user documentation, define user access and roles, embed in the organization management

• Educate & train users

• Continuously safeguard use of the organization best practices and architectural guidelines


Time to put the application live!