Want to learn more about these cookies? Click "Settings".
Projectapproach Phase 4: Technical- and functional analysis
To make every project plan a digital success, PHPro developed its own methodology: Our PHPro Roadmap. Today, we would like to explain phase 4: The technical and functional analysis.
These deliverables are:
1. High-level context diagram
2. Work breakdown structure
3. Functional Requirements Document
It is very important to get a better idea of what is needed. We always keep a good overview of all desired features, and whether the impact is realistic within the budget. Based on this information, we get a document that gives a clear picture of the features to be implemented in the software solution.
The document contains the necessary information in terms of
- Data manipulation
- Data processing
- Other integrations that will be performed digitally.
- Performance requirements
- Security details
- Limitations within which the platform must operate.
In an ideal world, user stories are already created in the discovery phase and incorporated into the Functional Requirements Document. This gives stakeholders a detailed description of the tasks a user can do with the software solution and provides more clarity and direction for the stakeholder(s). Usually, user stories are (further) developed after the discovery phase.
4. Budget estimate
5. High-level Project plan
While building a good picture of what our application will look like and especially what the requirements are, we look at how this can be implemented and where the technical difficulties lie. In the technical and functional analysis (which usually runs parallel to wireframing and design), the desired features are mapped out, analysed in depth and checked against the current setup, integrations, tools, plugins and APIs. In this way, in consultation with the customer and based on our functional and technical knowledge of the platform, combined with budget and planning, the scope of the project is determined.
Based on this analysis, we make a more concrete budget estimate and development can start.
The various workshops are determined during the kick-off meeting, and depending on the people who need to attend each topic, the agenda is set. Broadly speaking, according to topics are usually discussed, obviously strongly dependent on the business case:
- Architecture, integrations & basic set-up
- High level architecture
- Magento set-up
- Information architecture
- Product types
- Basis pages
- Header, footer & Navigaton menu
- Product model
- Category page
- Product detail page
- Shopping cart
- Search & search results
- Store locator
- My account
- Company structure
- Shared catalog
- Product details
- Master data
- Checkout processes
- Order flow
- Retour & RMA
- Search, CMS
- Search configuration for advanced search
- Basic / Advanced CMS features
- FAQ, About us, ...
- SEO, Legal & Reporting
- Technical SEO & Keyword research
- Reporting, tracking & dashboarding
What can you expect?
The end result of this phase is a document with an exact description of the platform to be developed.
The elaboration of this document is done in Confluence, and can therefore be followed and consulted online at any time.
After approval of this analysis document, a new estimate can be made for the next phases.
Turn your project plan into a digital success!
Do you have a digital project you want to make a success of? Do you also believe in a proven project approach as a solid foundation for a successful project? Then be sure to contact us!