Last week my company held its operations summit to review how we deliver solutions to our customers. We presented best practices and discuss tools, models, and approaches to understanding, designing and implementing software solutions. This discussion made me think back on how the ideals of methodology differ from the reality on the ground. Everyone can agree on the value of having complete, ironclad requirements before development begins, but we all know that this is unrealistic. Among the many ways that requirements fall short is that they are incomplete and inaccurate. Some requirements ultimately are thrown overboard because the cost of implementing them is higher than the business value, and others because they lead to a business process that is too complicated or otherwise unworkable. More recent methodologies such as Agile and SCRUM are more explicit about dealing with uncertainty. Perhaps we need to be more direct in dealing with inadequate requirements, setting a
From James Townsend, vice president of Sylogist, thoughts on digital transformation, marketing automation, customer relationship management, Power Apps , Microsoft Dynamics 365, government contracting, customer service and more.