Skip to main content

What is the difference between Customer and End Users?

In a lot of IT projects, Customer and End User contains the same group of people, even if in realty they are different. Because of this, we can end up very easily into a conflict between different scopes.
In today post we will take a look about the Customer and the End User of an application. We will try to define and discover what the similitudes and difference are between them.
The simplest way to describe this two roles is:
  • Customer: relates to the development process
  • End User: relates to product and services
TIP: You should never be end-user-driven, otherwise the customer will look as a ‘not team player’ – heathen person.
End User consumes and needs services brought by the product that you develop. For them, the application itself and the services/features from it bring the real value. In general, the source of revenue for customer is the end user that pays for this product. And in the end this feeds also the development team.
We can see a Customer, as a middle man between End User and development team, because they are not the consumers. In the same time, they play a crucial role. You shouldn't imagine the Customer as an external company, but is important to not have the Customer concept in the development team. We should have different teams and people. If we have the same people/teams we should keep in mind what is the role of each of them.
A customer can be seen as the role that takes the risks. For example he can identify a market opportunity, a lack of specific service. In this case he will risk and invest money in it. In this situations, Customer interest will be around development costs and delivery time. As software developer, you would expect a Customer to have a high interest in the functionality also, but usually the interest is not at the same level as costs and delivery time.
Because of this, the Customer should be involved in all process improvements areas (like retrospectives). His interest around development is not as high as we may expect.
In conclusion, we could say that customer is oriented to delivery, costs and processes. End User is oriented to application and what features are offered to resolve their problem (need). Knowing exactly who ‘plays’ the role of Customer and End User, we (as development team) can know exactly to witch role address different questions.


Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.