Empathy-A must have ingredient for a Software Recipe

Today, all activities and people interactions are continuously getting enabled by the touch of the software in one or the other way. This is applicable for Government interfaces with citizens, within organisations or organisations to public. As more and more people depend on the software, Empathy has become a must have ingredient for a software to be successful and usable.

Beyond the standard dictionary definition of Empathy, it implies many aspects for software industry , such as knowing what all types of users are going to use the software, in what scenarios they will be using the software, their work locations, environment, frame of mind, what will be their frame of reference while using the software etc etc.

Apart from all engineering practices which continuously get improvised, empathy is a must have from inception to operations for software. So time to interleave models and practices that help to give empathetic views for developers more formally into Software Development Life Cycle ?


Comments

Post a Comment

Popular posts from this blog

Transition Steps - Waterfall model to Agile(Scrum) model

  Transition Steps - Waterfall model to Agile(Scrum) model   Identify and orient the transformation program team Determine the program charter for transformation team Create Organizational Scrum guide Identify impacts from Organizational culture/values/management style Assess top down working style Bottom up engineering practices evaluation IT Infrastructure evaluation to meet Dev Ops needs and gap analysis Decision on pilot approach Vs Bing bang approach Communication plan for ‘Why change’ from Execs, Q&A with teams to the team Create change agents team Identify existing areas of ‘process waste’ and create plan to eliminate it Set transformation program obstacle handling mechanism Dev Ops and test automation investment plan Change management plan Identify the teams based on release dependencies, upcoming customer commitments, technology landscape etc. Review the program plan, approach, scrum guide and study findings with Exec team for project...
Read more

Continuous Delivery and Agile Principles

  Continuous Delivery and Agile Principles our  highest priority is to satisfy customer through early and continuous delivery of valuable software is the 1st agile principle. Let us evaluate how important this agile principle is. What are the benefits of adhering to this principle? If you want to de-risk as a service delivery team or as a customer to overcome business risks and build upon customer satisfaction, it is important to adhere to this principle as a delivery organization or as a customer. Continuous delivery of user stories with INVEST characteristics helps both customer and delivery team to be successful. When there is consistent and focused flow of information and deliverables across the requirement elicitation to software delivery, and then feedback on delivered software from customer back to the team, delivery team and customer are on a mission to meet customer’s business needs in the given environment. Continuous delivery helps team and customer to...
Read more