Archive for the ‘project management’ Category
The 10 rules of painless procurement - from both sides
Monday, November 15th, 2010
The 10 rules of painless procurement - from both side
A few weeks ago I picked up on a tweet about the tender process from @
As we had all been involved in the procurement process (from both sides) we decided to come up with a few tips on how to manage the process - if you are looking to submit a tender or if you are looking for a supplier.
We used a shared google doc to come up with several ideas, tips, experiences and these are our top 10 for both! I hope that you find it useful.
by Scott Hewitt, Tim McShane and Kevin Mulryne
scott.hewitt@realprojects.co.uk
kevin@mulryne.com
tim@fluffyclouds.co.uk
|
Rules for bidders (tendering for work and filling in the forms) |
Rules for clients (writing the tender docs and running the tender process) |
|
1 Make sure you are in possession of all the available facts
Ask to see the grid the team will be using to judge the bid so you can make sure you have each area covered. |
1 Know what you want
Ideas cost money and time. If you don’t know what you need it’s a specification that you should write, not a tender. |
|
2 It’s all in the preparation
Read the given criteria carefully and plan to match what you are producing as closely to the requirements as you can.
|
2 Tell bidders if they are likely to be wasting their time
If you are going to have a threshold based on company turnover (or some other criteria which will automatically exclude bidders) let people know.
Why allow people to write a whole tender when they are never really able to be a supplier? |
|
3 Be sensible with your time - and money
If you don’t like the tender, project or the idea behind it - don’t submit a response! |
3 Be open about your requirements
If you want environment, QHSE policy etc. explain why you want them and the relevance to the tender.
Provide bidders with a scoring matrix so they can concentrate their efforts on what you think is important. |
|
4 Pay attention to the process of filling in the form
Make sure you have plenty of time to write the whole return - uneven sections read badly and create a bad impression.
If it’s an online form, go in and get the questions then create answers offline to copy and paste in later - don’t try and compose answers ‘live’ on the system. |
4 Give bidders some guidance on word count
Consider limiting the number of words for each question - this will make returns easier to compare and focus bidders’ attention on what you think is important. |
|
5 Be a bit pedantic about language
Check spelling, punctuation and grammar - mistakes can put off the more exacting employers - or those who are looking for ways to differentiate between close competitors. |
5 Make it simple
The PQQ is meant to be an introductory, pre-qualification process. 40 page documents are not helpful to anyone. You will get stock answers.
Why not have an initial, high-level PQQ that covers the main important issues? If you pass that then provide the more detailed PQQ. |
|
6 Answer the questions which are asked, where they are asked
Answer the questions which are given - don’t give ‘stock’ answers copied from elsewhere.
In multi-part tender returns, write a new answer for each section - don’t copy and paste between sections as they will probably be read by the same rater and this can give a negative impression.
|
6 Be transparent about money
While you want best value, providing an indicative budget allows clients to be innovative within a framework.
If you have a budget of £20k and then receive ideas which cost £60k that you can’t use everyone has wasted their time and effort. |
|
7 Keep it real
Only use real evidence - exaggerated or invented experience can be checked - especially when you are in a small area of work - the rater may well know the situation you are exaggerating/inventing details about! |
7 Keep it real
Don’t run a procurement process and ask for tenders if you don’t have the budget to do the project.
Also just getting quotes for comparison and having no intention of using the client for a real project is unfair. |
|
8 Raters are people too!
Remember that if a team are looking at a bid then some of them won’t be experts in every area so write for them as well as for the experts. |
8 Use realistic and fair timescales
Be sensible about your time deadline. People need time to put a tender together.
Also if you set the tender make sure that you meet your own deadline for feedback and decisions. |
|
9 Use your best people
Each section of a bid will be reviewed - potentially by an expert. Get an expert at your end to look at the bid so it isn’t obvious that sufficient time hasn’t been spent on key sections.
|
9 Respect your bidders
Provide detailed feedback on successful and unsuccessful tenders.
Respect ideas and concepts within a tender response. If you want to use them, you should pay for them! |
|
10 Check it…and then check it again
Make sure you check the document you are sending out. One of us found someone’s comments left in saying, “No one will read this section so just put anything in.” Needless to say….
|
10 Play nicely
It’s a relationship - you both need each other. Be clear about what you both want from the project. |
Testing, testing, testing - what is more important the test or the content?
Thursday, September 3rd, 2009
I’ve have just finished reading a book at the British Cycling team and their meteoric rise over the past 10 years. As a keen cyclist the book provides a number of insights into how the team operated. There is one section in particular that raised a number of questions.
Sir Chris Hoy started to compete in an event called the Keirin several years ago when the Kilo event was removed from the Olympics. For those of you who have caught a bit of track cycling on the TV it’s the one where they all ride behind a motorbike at increasingly high speeds. The cycling aficionados amongst you will know that Keirin originates from Japan and is remains hugely popular. Kieran riders earn vast sums and enjoy celebrity status due to the massive amounts that are bet on the outcome of races. Increasingly overseas riders saw the money on offer and wanted to compete in Japan, to date without a great deal of success. Before any overseas rider can compete in a Japanese event they have to undertake a rigorous 2 week training camp, where one of the tasks involves taking a bike to pieces without dropping a tool and re-assembling it in a set order.
At the end of the 2 week course there is a test. Pass the test and you can ride in events, fail and you can’t. Simple.
It was the test aspect of the course that interested me the most. One of the cyclists commented on the monotony of the course and the sheer basic nature of the course content…but…he remained ‘switched on’ at all times as if you didn’t pass the test you couldn’t ride. The rider attended all of the sessions, took everything on board, put up with the monotony to ensure that he was ready for the test. He took the test, passed and rode in events.
Reading this particular chapter really made me think of all the courses where the qualification is vital to future success and progress but the learning experience is often disappointing for those involved. I’ve spoken to my friends who have attended courses that have not been challenging and focused purely on getting the badge. I’ve also got my own experience to share. Over 5 years ago I took my PRINCE 2 exams; the first 2 days pretty much consisted of highlighting pages from the course book. I was somewhat disillusioned by this and in the revision periods at the end of the day I actually tried to gain a deeper understanding of what the course was about. It was only at the first multiple choice exam that I realised what I was being prepared for. Each of the sections I had highlighted had been linked to potential answers in the multiple choice exam. Once this was passed the whole teaching style changed as we approached an open book written exam. I’d not thought about this course until after I’d finished reading the Keirin chapter and it all came back to me!
creating an e-learning strategy - a few things to think about
Wednesday, July 8th, 2009
Over the past few weeks I’ve answered questions about e-learning strategies. I have been involved in the creation of e-learning strategy documents and projects for the public and private sector in the UK and thought that I would share a few of my thoughts.
This isnt’ an exhaustive list but it will provide you with a starting point. I would ensure that any strategy focuses on a number of key areas, these are going to be specific to your organisation but you may want to think about the following:
Participation
Who are the affected parties? What additional training provision will you need to put in place during the project lifecycle? Who are your stakeholders (internal and external)
Technical Issues
What is the current IT platform? How will your e-learning strategy integrate with future IT changes and developments? You need to think about how these are aligned
Content creation and acquisition
Where are you going to get content from? Are you going to develop it internally? What will your quality standards be? You need to think about the creation of e-learning guidelines so that you can control the output.
Feedback systems
How will you measure performance? How will cost of ownership and return on investment be measured? What are the projected costs? How will effectiveness of the learning be measured?
Costs
How will ROI be measured, how will you work with the cost centres within the business
Limitations
Think of the issues that you might have and get these highlighted early
Types of learner
Several things to think about: IT literacy levels, mobile learning, expectations of e-learning
Business Improvement
Where will this be? Cost, Improvement in access to training material, process efficiency?
There are obviously many other things to consider, some of which will be specific to your organisation but but hopefully this will give you a starting point.
hello readers of the blog!
Tuesday, February 3rd, 2009
I’ve been on the road quite a bit recently and I’ve bumped into a number of friends and colleagues. IT was nice to get comments that people actually do read the blog!
Hello to all of our readers….I’m not sure quite how many readers we have!
At learning technologies I saw Clive Shepherd deliver his seminar on e-learning in a downturn. He mentioned blogging and how you needed to be prepared to contribute to the blog regularly, how right he is! I’d like to blog a bit more than I do but it is quite tricky to do this every day, although I’m going to try to make a few more blog entries than last year.
This month I’m making the final touches to the first norfolk e-learning forum event of the year and we are working on a number of projects in the public sector. I’ve also taken some time to write a series of short articles about project management which we might upload to the website.
Thank you for taking the time to read the blog, I hope that there is something interesting from time to time…
oh….I bought a PSP at the weekend so we planning to do some R&D as well as road testing an acer aspire one. My first acer aspire only lasted a week before the screen blew!
no more i6 for basecamp
Monday, September 8th, 2008
A few days I logged into my Basecamp account to be greeted by a new page…bascially they are stopping support for IE6! Ok, so more and more people are on IE7, Safari, Firefox with Chrome coming soon but I was still surprised.
I had read a few articles recently where users had come across websites which no longer supported IE6. Ill still be able to view Basecamp via another browser but it got me thinking about a lot of our customers. Many of the organisations we work with still use IE 6, if they are in big companies IT roll-outs can take time.
I understand why people aren’t continuing to support IE6…I have it on my machine as I’m the company IE 6 tester…but it did get me thinking about how websites could fail to be supported on a browser in a matter of months. Could we reach a situtation where developers are coding sites for specific versions of browsers with the user selecting their browser before they enter the website? I’ll be watching what happens with code standards and the increasing number of browsers coming online.
e-learning - managing change and test requests
Wednesday, September 3rd, 2008
so you agreed the spec, got the contracts right, got the team in place and then you’ve started work. Everything is going well but you know that you have the first review coming up. How do you manage the process? What is going to be documented? How will you make sure everything is done?
We’ve started using a really simple excel sheet for logging all change and test requests. Each entry gets a unique ID and we record:
The problem, the requested change, browser type, operating system, wider impact of the change, who requested it, screen grab (with a reference),who did the work (in our office), any url or reference and any additional notes.
We’ve found this to be really useful when we manage changes. Giving everything a unique ID and sharing the sheet across the development team means that we can track a change and also have something to refer to. Instead of saying has the menu been changed we can ask about 1.1-12. It might seem a bit long winded, especially when you start but if you’ve got lots of requests to manage it is really helpful.
Scott
elearning project management - what did we need?
Tuesday, September 2nd, 2008
Before we made the move to Basecamp we did do some thinking about the tools and features that we needed. We looked at a several tools and decided that we wanted to have the following functionality:
1: web based so that our clients could use it without having to buy and install software
2: email notifications so that the system could deal with some of more the basic notifications
3: secure, safe and reliable service - managed by someone else if possible
4: store files so that clients can download them
5: ability to store multiple projects and multiple clients
After a review of several tools we went for basecamp. As an elearning company we were also impressed with the online instructional videos. These saved a great deal of time when training staff and our clients. There is still a challenge in getting everyone to look at the project plan but the easy layout and email notifications makes it a lot easier to encourage use across the project team.
project management in elearning….what to use?
Monday, September 1st, 2008
It has been about 6 months since we started to use Basecamp. After years using Project and creating massive Gantt charts that were:
Hardly ever read
Rarely updated
Over about 20 pages when printed
We made the decision to use Basecamp. It doesn’t have all the features of project but we’ve found the functionality elements of emailing, file uploads and chat more than make up for some of its limitations. We’ve foudn our own way of using it and it is working well for our clients who can get an instant update and get email notifications.
I’ll still revert to project when there is a ‘big’ project to plan with lots of depedencies and critical path as Basecamp doesn’t allow this at the moment but basecamp is proving popular.
The real winner for me was the instructional videos. I think that they are excellent, we’ve used them in our project manager training and they have also saved loads of time when we’ve brought the client into Basecamp. As they are always available you can revert to them at anytime. Chatting in the office we can’t recall a piece of software that was so simple to use but delivered so much in terms of efficiency and business improvement.
I’ll always have project on my machine but it is basecamp that I’m using day to day.

