Culture Book - Flipbook - Page 15
14
13
Building the culture together
“In working on the internal implementation of an Intranet using SharePoint, I initially experienced
some differences in opinion between the ‘old’ Innodevers and ‘new’ Innodevers on the details
of the implementation.
I got the sense that the ‘old’ were feeling that they were being taken over and left behind. As
the project progressed and by including both the ‘Old’ and ‘New’ Innodevers in the process,
I noticed that the platform or technologies weren’t all that mattered - it was the sense of
‘Innodev Teamwork’ and a drive to a common goal that really counted.”
Our clients recognise our professionalism
“I’ve been working at my client for a while and in my last engagement with them, I had an
opportunity to provide an estimation for an upcoming Dynamics CRM project. Through the
reputation I had with them and the way Innodev deals with the client, they did not challenge
my estimation and accepted it because of my thorough justification. I am looking forward to
hearing some good news from them soon.”
Great communication leads to trust
“The client needed a GIS/Python expert to customise a vital workflow and engaged us based
on previous positive experiences.
Collaboration
The initial engagement was to provide a design which entailed a fair amount of scrutiny. They
then asked for us to build the workflow, which I did among schema changes, infrastructure and
third-party provider issues. I kept communication and documentation to the bare minimum,
but always answered the client’s questions, including what were the recent achievements and
obstacles, what’s left to do, how much budget is remaining, how do you build, test, deploy,
etc. There were no surprises for them at any stage and the documentation (which was part of
the codebase) answered every technical question they required info for.
“As a recent arrival to the company, I was asked to work
on various bids for business development and I realised
that we did not have much base content to put together
the actual bids. Other companies that I had worked at
previously had lots of collateral available, but we seemed
to have lots of ideas in peoples’ heads and a lack of
readily available corporate history.
The only issues reported by the test teams were related to infrastructure and the project was
accepted by the client. There have been subsequent requests for enhancements and the client
is in the process of arranging permanent access and a support agreement to continue the
engagement into the future.”
I had noticed that despite missing the key components of
corporate history and collateral, the desire to collaborate
and work with each other to get to the outcome was a
strong one. Without that desire to collaborate and help
each other, despite personal workloads, the journey to an
outcome would have been a much slower one.
As a result of the team pitching in and pushing to deliver
the outcomes, we are starting to build up a library of
content that we can re-use for business development
bids, making the process of generating a bid response
more streamlined and effective.”