Custom Project Types
Conventional project type or agile software development?
By all means matching to the requirements of your web or software project.
Deciding between a conventional sequential project type (requirements analysis, implementation, quality assurance, handover) and an agile project (multiple iterations to approximate the optimal result) a few variables must be taken into account. Among general factors like project scope, goal and featured technologies, code outsourcing requires a look at the overall project outline: availability of designs, functional briefing and product specifications.
Conventional Project – Fast and Easy
The conventional project type is ideal for templating projects with existing designs and functional briefing: Upload Design - We code - Download Template. Center point of the conventional project is routine: At project start you define the work package, we code the templates and the next thing you'll get from us is the download link. – Perfect for designers and agencies that have enough website concept experience and just need a technology partner who focusses on implementation speed, reliable timing and consistent code quality.
Configure your Project
You can trigger the easiest project initiation through our Configurator. It only takes a few minutes to click through the packages and options and upload your design files. The project starts immediately and a few days later you can download your templates.
Individual Effort Estimation
If you can’t describe your project requirements within a few clicks, just ask for an individual quote. Upload all available design material, add a note to us and we'll call you back immediately. After coordinating any critical aspects, we create a binding estimation of all efforts and timings. This guarantees an accurate implementation setting which our internal quality assurance team uses as reference.
Early Problem Recognition
When creating PSD designs the greater vision and basic implementation knowledge is essential. It happens that webpage elements are being designed deviating from established standards. Not to reproduce a specific use case, but as the result of unawareness of the technical constraints.
A late change is often difficult, causes more costs and time delays in the project. Our project managers know these scenarios and are glad to help you to find a solution for requirements inconsistencies or missing designs early in the project.
Agile Development – Flexible Requirements
Agile project management is the right choice in case the website’s requirements exceed simple rendering of static content, and if the implementation requires fully fledged business cases, workflows or complex commerce applications.
First we verify the feasibility of your concept and provide a first estimation based, for example, on mock-ups and functional descriptions.
After receiving your approval, a first prototype of the base system is being developed. This system offers enough functionality to be able to get a clear picture, to test the look and feel and the workflows, and even be presented to investors.
Now the iterative process starts. Depending on your impression during the implementation / test phase, the project proceeds to your liking. You can witness how the website grows, module by module, so you are making sure the resulting product matches your actual business case.
Controlling your Budget with Fixed Prices
For each project phase and each module you'll receive a separate fixed price offer. This will give you the advantage of using an agile project’s wide performance and flexible handling while at the same time keeping full control of your budget.
At anytime the project’s dynamics allow to shift the focus towards new, seemingly more important functions, or to move less important features into a later release. This way, we ensure that the project resources are targeted at a product that resembles your growing idea as close as possible, creating a highly usable website that matches your business case – from day one on.
Prompt Reaction to Changes – A Scenario you might already know
The concept defines some user management with simple permission system, but later these requirements change: An additional super user is needed, a new permission level and a feature to define representation rules follow.
Implementing such a change is complex and expensive, potentially disables the original system architecture, and typically causes new problems somewhere else in the system. If these new requirements had appeared during the development phase, an agile project would very well allow for immediate consideration. Impacts at other areas and the timeline complications would be apparent right away.
Your Project with Codingpeople
In reality there are many variations of project types' applications. A conventional project with agile kanban tools (simplified visualization of team members' tasks) or SCRUM projects with detailled feature specifications are not uncommon, and reflect the true world of web projects.
The following table compares the advantages and disadvantages of the two methodologies so you can decide for yourself which key aspects are important to you:
Conventional | Agil | |
---|---|---|
Pro |
|
|
Contra |
|
|
Maybe “SCRUM light” is the right method for you? Or you have detailed concepts and designs available and just need a swift implementation while peeking into the development process?
We know the day-to-day business of marketing and internet agencies and enterprise IT departments by heart and will arrange the perfect project mode together with you. Give us a call at ++49 – 30 - 609 8855 60, or upload your designs beforehand for an individual quote.
Upload Designs — We code — Download Templates