Design Fault, Scope Creep, Moving Insight or Unexpected Success?
Once upon a time, I created a Team Site to facilitate a global project. It was based on a custom list where global and local people could enter project data, such as business unit, product, and a code from a choice column. The code represented a number. I suggested to the project owner that we add a column with the number corresponding with each code, to enable an automated calculation of the value of the item. *1)
The process owner did not think that was necessary. He wanted to keep things simple and would do the aggregated calculations via an Export to Excel.
Testing and feedback.
When the lists and specific views had been created, I asked the process owner to test and discuss this with a selected number of the 50 designated users. He came back with some good feedback and change requests. We ended up with 4 custom lists, each with the same structure, but with different values to select from.
So far, so good. We launched the site.
Shortly after introduction the site started to fill with entries. The only negative comment was when one person was flooded with Alert emails when someone bulk-uploaded 500 entries. I showed him how to change the default “immediate” Alert into a “daily summary” and we happily agreed this was a sign of success.
After some weeks, I noticed that Excel files with the required information were being uploaded to the site and updated online. It turned out that many business units had been doing this same exercise already on the business unit level, and thought they would share and update their work (which had been done in Excel) in our site. I would have preferred them to add their data directly into the lists, but it was a good sign that the business units wanted to share.
You can imagine what followed: ”How can we upload the content in those Excel files into the lists?” It was not too difficult to create an extra Datasheet View with all mandatory columns, export it into a Template, and write a short manual on how to copy the content from Excel into the lists. *2)
Meanwhile, requests for access kept coming in from across the world. There were now about 200 people who wanted to share their data instead of 50. Great!
The site also got senior management’s attention. They wanted to show the real-time project results on the site’s Homepage so everyone would be stimulated to add to the numbers. Yes, I could understand that wish, but it meant that I had to add that extra numerical column in each of the lists after all (that the process owner had decided to leave out in the design phase) as well as a calculated field, and change all the views and templates. That was not too bad, but someone had to update all existing 1500 entries with the corresponding number.
A volunteer was appointed to do just that.
But wait…there’s more!
Just when I thought the whole setup was stable, the process owner approached me and asked me if we could capture two other values in the list while we were collecting data.
For me this was 30 minutes work, but for him it would mean that he had to communicate a change, re-educate everyone, and revise the input template and the manual. And for all business people it meant they would have to find out those values, revisit their entries (by now we had about 4000 entries) and update them. The “volunteer” could not do it this time, because the values were not as straightforward as the code.
He decided not to do it.
What do we call this?
It all worked out well in the end, but I have wondered what this is.
- Is it Design Failure because we did not envisage properly how the site and project would develop? Should I have been more insistent on adding that numerical column from the start since I knew that would come up? Still, I could never have foreseen the wish to collect those two extra values.
- Is it Scope Creep because the process owner had not set enough boundaries for what he wanted to achieve?
- Is it Moving Insight because the organization learned what you can do with SharePoint as they went along and it was only natural that they wanted to make the most of it?
- Is this an Unexpected Success because it worked well and we should be happy that it sparked so many new ideas?
- Or is this just The Way These Projects Go?
This is something that I have experienced more often and I never know whether I should be happy about it (because it shows people learn about the possibilities of SharePoint) or sad (because it shows what we are not so good at project definition).
This is the reply when I asked the question on Twitter:
@ellenvanaken Emergent requirements with an agile development process in line with increasing maturity of the user population. (Nicely done)
— Chris Tubb (@christubb) November 9, 2012
What is your experience and how have you dealt with this?
*1) The drop-down had too many items to enable an IF, THEN formula to calculate the number. Next to that, there was a “specify your own value” field if the project had a non-standard code.
*2) I thought connecting the Excel to the list would be too tricky for most users, and I also did not know how SharePoint or our system would react to so many simultaneous connections
Image courtesy of Ambro / FreeDigitalPhotos.net