polcode’s (not so) secret recipe for an efficient software development process
TRANSCRIPT
Polcode’s(not so) secret recipefor an efficient softwaredevelopment process
Why do we receivesuch positive reviewsfrom our clients?
It’s our soware development process that combinesthe best of Agile methodologies & 10 years of experience.
Sounds complicated? It’s actually very simple!
Let’s go through it step by step.
…, but first - why Agile development?
It’s a set of soware development methodologies that: stress the value of communicaon between all individuals, assign and define roles for everyone, encourage iteraon, that is, gradual improvement of the project based on feedback.
As a result, Agile software developmentis an approach used by developers who care not just about the code quality,but also about the commercial and strategic success of the final product.
And that’s why we love it so much.
See how it fits into our very ownsoftware development process!
ENVISIONINGPART 1
How would you like the project to look?
Take your time. We are going tothoroughly gather information through:
- conversations,
- webinars,
- emails,
- sharing - sharing existing documents,
- mockups,
- wireframes.
SCOPEPART 2
Here we: - ask a series of clarifying questionsto understand your needs,
- learn about the user base, your business...
- … and design the information flow as wellas all the other workflows of the system.as all the other workflows of the system.
ROLES & STORIESPART 3
By making full use of Agile’s best pracces, we:
- assign roles (in Agile development, everyproject member has a clearly defined role),
- write user stories, (descriptions ofwhat end users will be doing),
- write epics (more complex descriptionsof major building blocks of the project).of major building blocks of the project).
CLIENT STORY
EPIC
THE GOLDEN MEANPART 4
All of it allows us to pick:
- optimal business solutions,- the most relevant technologies,- the most trusted configuration,- the most effective techniques,- the least time consuming d development process,- the most reliable components, including 3rd party integrations.
SIGNED, SEALED...PART 5
That’s what the
Statement of Work
and Master Service
Agreement are for.
Now we can esmate cost and share responsibilies.
RESOURCE ALLOCATIONPART 6
With the deal sealed, we can confirm resource allocaon.By this we mean which developers will be responsible for the project and to what extent.
We prepare an inial project specificaonthat includes:
- a list of modules of the new system, their interaction and interdependence,
- attributes of the components, functionalities, formats, capabilities,
- limitations and definitions of the system.- limitations and definitions of the system.
PROJECT SPECIFICATION & CONFIRMATIONPART 7
THE ENVIRONMENTSPART 8
When our developers get to work, they dividedevelopment into four separate environments:
1) DEV environmentwhere the software is actually built by our developers.
3) STAGING environmentwhere the functionalities are verified using data.
4) PROD environmentwhere end users access the software.
2) TEST environment where the client gets to see and test the fruits of development.
It’s essenal for Agile. We report both to theclients and to each other to keep everyoneon the same page:
Regular sprint planning meetings take place(usually in the morning) to define task completionrequirements (so called DoDs - definitions of““done”). The software built in the DEVenvironment is subject to review from the client.
REPORTINGPART 9
The reason why Agile is so good for theclient is that it accounts for the fact thata lot of new things can be learned duringdevelopment:
Clients may realize that some featuresare not necessary, while some othersare missing. Designers mare missing. Designers may find outthat some of their choices don’t proveto be effective in practice.
Every meeting is another chance todiscuss the problems and change thescope to solve these problems.
ITERATINGPART 10
LAST BUGEliminang errors in the producon versionis the essence of cut-over acvies.We do it because:- going live or implementing extensive changesto large systems can be tricky,
- data migration and conversion may be necessary,
- it’s the last chance to spot errors before the first- it’s the last chance to spot errors before the firstend users can do that.
CUT-OVER ACTIVITIESPART 11
STABILIZATIONPART 12
Going live can be stressful.Polcode relieves it by:
- extensive testing every step of the way,
- carefully monitoring the performance of the software (stabilization phase).
… DELIVERED!PART 13
Is everyone satisfied with the project? To answer the question, we all gathertogether at the closing meeting.
A formal project sign off takes place wheneveryone answers “yes.”
That wraps everything up :)
FOLLOW UPPART 14
Even when the soware is up and running,we sll follow our clients in order to:
- ask whether there is room for improvement,
- advise on possible upgrades and patches,
- celebrate new success stories!
The entire system is designedto learn all we can about yourproduct, use the power of ourdevelopers to make quality
software and test the hell out of it!This is how we roll.
By the way, since you made it this far,we would like to admit that we did hide something.
The real secret behind our process.The thing that guaranteesour quality and success.
Wanna know what it is?
It’s an incredible and the most reliableerror spoer a developer can have at their disposal...
Can you guess what it is?
Ah, enough suspense already.It’s:
?? ??
The ulmate error spoerand final weapon against errors!
thePolcodeDuck
Really, that’s all we have...well besides amazing and experienced developers combined withachievement-oriented management.
Now you know the enre secret behindthe Polcode Soware Development Process!
