Skip to main content

Software in Kilograms

Software is by far different than tomatoes!

Software development depends heavily on the following factors:SWinKilos

  • Requirements clarity
  • Business complexity
  • Client maturity
  • Team understanding for the requirements
  • Team experience
  • Team productivity
  • People mood
  • Technology
  • Aiding tools availability
  • Company processes and strategy

Any of these factors or the combination of these factors can heavily impact the project and its estimate. I am not saying that we cannot estimate projects, I am saying that we cannot estimate accurately, and even if the estimate is accurate, given other circumstances, the same estimate may not be accurate.

The major difference between Software and other merchandises is that Software cannot really be measured. There were and are many efforts and theories trying to quantify Software and measure it, yet there is nothing accurate. Software can be measured by complexity, lines of code, effort, features, points… too many theories and models, yet none of them suggested measuring Software in Kilograms!

Grocery Model

Given the fact that no 2 developers with the same skill set and years of experience can develop the exact same application using the same requirements, clients don’t trust/believe the time and cost plans vendors provide for their projects and they always bargain these plans and push on vendors to reduce the cost and shorten the time duration whether it is acceptable and achievable or not.

Clients bargain as if they are at the grocer’s choosing tomatoes for dinner! They bargain as if they understand how Software is made. Unfortunately, many PMs allow their clients to behave in such a shaming manner and also encourage them to do so by the unethical tricks they use to manage projects and clients. Some PMs abuse their clients and use the intangibility of Software as a double edge weapon which the client can also use to fire back on vendors.

These PMs introduced the Grocery Model in the field of Software Development. The model is simple in definition, and at the same time very difficult to apply. The model totally depends on the bargaining power and negotiation skills, it has nothing to do with actual Software Development, processes or the proposed effort and cost.

The Grocery Model is driving the Software field into an abyss of no creativity and no serious work. This model empowers the Hit & Run concept and destroys vendors differentiators, reputation, and long term relationships where all parties benefit from the work done and produce good Software.

Labels:

Comments

Post a Comment

Popular posts from this blog

The Triangle of Tactics

Sometimes referred to as the Triangle of Horror… where the PM tries his best to maintain his balance while walking on the very thin project rope between this triangle and the Project Constraints Triangle (time, cost & scope). The triangle sides represent: The Team, The Client and The Management Every side of this triangle is obsessed by the sole idea that the other two sides want him dead, i.e. the team thinks that the client and the top management want him dead and vice versa. Usually a good PM gets lost while trying to maintain this triangle in good shape to keep all parties satisfied and happy while making them think they are his first and only priority to get out what is needed from them for the sake of the project. From my perspective, this is a much harder balance to keep rather than maintaining and managing the Project Constraints Triangle… It highly depends on people, their culture, maturity level, and on the PM’s ability to understand this and deal with it in a
4 comments
Read more

I am a Project Manager

I am a Project Manager and I love my job… I am a project Manager and I love doing my work! I am nothing more but a Project Manager amongst many others. I got married to my work (not job) after a great love story which started from early childhood ( coming soon ). I started my career as a Software Developer in the late 90s, then held many positions in the field of Software Development, some were promotions and some were kind of additional assignments due to my performance. Among the positions I held are Developer, Team Leader, Project Manager, Project Leader, Senior Project Manager, Senior Project Leader, Program Manager, Business Analyst… though I was dreaming about becoming an Architect! But seriously the job I loved the most is Project Management. The things I hated the most in my early years were politics and economics/finance, which both became the core of my daily work for some years now! 94% of my experience was built by working in Software Houses as a vendor/provider and
4 comments
Read more

5 Reasons not to listen to a PM (for Managers)

Usually a PM cares about his projects and is keen to develop them as per the planned budget, time and scope. However, managers should not listen to their PMs for the following reasons: 1. PMs are Time Wasters PMs plan… They study and mitigate risks and project issues in proper ways to guarantee the smooth execution of the project. Planning is a bad practice that PMs should stop using and referring to whenever they discuss a project related issue. Plans are not really needed and in most of the times they are useless because no one follows them (all gratitude and respect reserved for PJs). Also, it is preferable to face risks when they fire. Anyways, who really cares for risk mitigation and contingency stuff! Let’s face surprises when they arise and use panic mode to push on teams to solve their issues! 2. PMs Forecast PMs track their projects and use trends, issues, project and client historical data to forecast project status and use corrective actions properly to maintain thei
3 comments
Read more