510 Followers
·
Follow

What I learnt working on IT projects

Image for post
Image for post

Don’t build solutions on assumptions, ambiguity and ignorance #HoskWisdom

IT projects are a challenge, a good deal of fail and all of them are difficult. IT project can need lots of people, time, ideas and hard work.

Projects face obstacles, problems and changes of priorities, these changes can defeat you or you look at them as opportunities to make the solution better, the quote below sums it up.

“The obstacle becomes the path” Ryan Holiday

Challenging projects help you see the best in people, you can’t deliver a project by yourself and at certain times different people will shine, save the day and do something that helps you. Your team will be there to help you when you need it and you will be there to help them.

The better you can work as a team, the better the project will go.

Projects have taught me about myself, about technology and how to work with a group of people to make a team.

IT projects are about people not technology

There is a lot of noise and focus on technology on IT projects but ask yourself these questions

  • People builds the solution
  • People use the solution
  • People make decisions
  • People sign off requirements on the project

People are at the heart of the project and they are reason it for its success or failure.

Slow down to speed up

More people, working hard feels like it would speed up delivery but it can slow things down, when work is half finished, changes conflict.

Focus on quality rather than speed of output, fewer mistakes and consistent delivery will create releases, the successful process builds confidence and creates momentum.

Surprises on a project are never welcome because problems and delays follow. Focusing on quality, reducing mistakes and keeping momentum raises confidence in the team, it will reduce the chance of unexpected surprises..

Understand the business goals

Before you start with the technology and solution, understand the business, it’s goals, it’s language and how the business wins.

The purpose of the solution is to create a tool to support users do their job and the business to achieve its goals.

All requirements, features and user stories should focus on business needs and purpose. What is the user doing? why are they doing it? and how does this help the business.

Ask questions

Ask questions, to understand the business, clarify assumptions and work out the goals of the business.

If you have a question, ask it, it’s likely if you are thinking this then others in the room will be thinking it. Question help understand and clarify assumptions. Avoid building the solution on assumptions because these are weak foundations that could crumble later.

Don’t remake the old system

Everyone is influenced by the existing system and they will try and recreate the old system with new technology. People are use to the current system, they understand how it works and resisting change is the comfortable

Focus on the business goals and what the purpose of the business. The old system will be aligned to the functionality of the old system. When creating a new system it’s a chance to align the process with the out of the box functionality of the software it’s being built with e.g. Dynamics 365 and Power Platform.

Don’t be constrained by the existing system, focus on the goals of the business and how best to deliver those and make it easier for people to do their jobs.

Warning — it will be difficult because people don’t like change and will keep referring back to how the current system works.

The best way to learn is through questions, reframe questions to look at work from the perspective of the teams and persona’s doing the work, understand the goals of the teams and how they fit together as a whole.

Clarify assumptions

Assumptions lead to problems, bugs and changes. You need to clarify the assumptions and get the facts otherwise you will be building a solution on ambiguity and ignorance.

Clarify the assumptions as soon as you can because these are logic bugs and can embed themselves in key parts of a process, which can be difficult to change later.

Focus on what matters

In a chronically leaking boat, energy devoted to changing vessels is more productive than energy devoted to patching leaks. — Warren Buffett

People devote energy to unimportant and unproductive areas. Work out the key areas and focus on getting those right, focus the energy and stop wasting time on the other areas.

Most areas on a project are unimportant and not worth arguing and discussing.

“You cannot overestimate the unimportance of practically everything.” Greg McKeown

People will try to create meetings for everything and demand your time. If you are not needed in a meeting, don’t attend and spend that time doing productive activities.

Keep it simple

Show the users how Dynamics 365 works, start with a simple solution and then get users to try it before thinking about any complex solutions.

When you give users a blank canvas and ask them what they would like, they will come up with ideas that sound good but aren’t what they need and aren’t easy to build or maintain.

Align the requirements to the out of the box functionality.

Don’t panic, don’t blame

Panicking causes you to make bad decisions, blaming doesn’t achieve anything and lowers morale.

Be prepared for things to go wrong, mistakes to be made. Projects involve getting out of your comfort zone and trying things we haven’t done before. Take this small knock backs on the chin, pick yourself up, dust yourself down and try again.

You can’t guarantee to get everything right, particularly when you do something for the first time. Trust the team, trust yourself, don’t lose faith and keep going.

It will be difficult but you will overcome all the problems in your path. You will do it as a team.

Projects can be difficult but Don’t quit

IT projects are difficult, there will be tough periods but keep going and do not quit.

There will be times when you think the project won’t succeed, the deadlines are too tight, requirements aren’t defined, too many bugs, priorities changing, people leaving, technology failing, super bugs making everyone working from home.

Keep going, don’t quit, you will get there.

Relationships are key

Relationship with the customer and users is important because you want build trust. The customer pays the bills and makes the decisions, you have to influence as the technical export.

Build a good reputation and relationship with the client. This means listening, giving information and building trust. Avoid things which can reduce confidence in your ability, things like

  • Bugs
  • Not replying quickly
  • Hiding information
  • Talking in technical jargon they don’t understand
  • Raising problems without solutions

The customers in an IT Project is not the enemy, they are the partner. You will work together to create a solution

Conclusion

IT projects often start slowly which is fine, as long as you keep improving, fixing problems and build momentum.

Projects are not the same and there is no template to deliver a successful project. You have to adapt to situation, people and requirements. Build relationships, gain trust and find a way to progress.

As relationships grow, the project team can work quicker and the work becomes more rewarding.

Projects are about people, they will be the reason for success.

Written by

Have been working with Dynamics 365 since version 4 and enjoy reading and delivering enterprise projects

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store