Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download Session 12 - Communication in the Software for BS Development
Transcript
UG 2015 Session 12 The Importance of Communication in the Software-for-Business Solutions Development Presenter: Phlip Pretorius Date: 17 March 2015 Note: This presentation is about KNOWLEDGE Personal Disclaimer • The presentation is based on my personal experience, observation and research __ • It does not necessarily reflect the opinion or policies of Adapt IT It’s better to be roughly right than precisely wrong! John Maynard Keynes Story of Our Man Flint (OMF) The doctor never checked the size of OMF's underpants • How relevant in his situation? • Unknown elements that causes unhappiness • Case Study – A client and SLLL • Sometimes there is a lack of KNOWLEDGE about what the client really need. Adapt IT Software Development: The current situation • This is the description of an extreme scenario – Does not occur often. – Not all clients – Not all developments Adapt IT Software Development: The current situation Adapt IT Software Development: The current situation Adapt IT Software Development: The current situation Adapt IT Software Development: The current situation Adapt IT Software Development: The current situation Adapt IT Software Development: The current situation Adapt IT Software Development: The current situation Adapt IT Software Development: The current situation Adapt IT Software Development: The current situation Silence = No Communication Adapt IT Software Development: The current situation • Why is it like this? – Lack of effective communication Adapt IT Software Development: The current situation • Effectiveness of Communication How can we improve the situation that I described? • By Effective communication – We need knowledge of the business environment – Knowledge is shared via communication – How can we effectively share knowledge? How can we improve the situation that I described? • Osmosis How can we improve the situation that I described? – Osmotic Communication How can we improve the situation that I described? – Osmotic Communication How can we improve the situation that I described? – Why is osmotic communication important? • We get INFORMATION that can lead to KNOWLEDGE – Case Study: The Programmer, Graduation, Academic Application and I. – Will Osmotic Communication work between Adapt IT and our clients? The reality of location - We are far apart • Two challenges – 1. Cost of business communication • Erg-seconds – Refers to the amount of energy it takes to move an idea from one mind to another – The term “erg-seconds” captures the cost in both labour and time to get a question answered • It indicates that project costs increase in proportion to the time it takes for people to understand each other. The reality of location • Two challenges – 2. The “Lost Opportunity Cost” of missed early interventions. The Agile Way • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan The Boat Trip The Boat Trip The Agile Way • Joe Little recently made a great analogy in his blog. – The customer is thirsty and wants a drink now. – The customer doesn’t want to wait three months for a delivery of 200 water bottles … just a drink now, please. – This is a practical definition of Agile. • Release a small set of features • in a few days or weeks • instead of a huge set of features six months or a year from now. The cost factor • The Iron Triangle of project management – a model of the constraints of project management • What will you deliver, how much will it cost, and when can you get it to me • Changing an input to any one of those will impact one or both of the others – The Demise of the Iron Triangle The cost factor • The Iron Triangle of project management “You can have it good, fast or cheap. Pick two” Is there an Alternative? • Think differently. Is there an Alternative? • My proposal for Alternative development route – Client define scope • Categorise in priority • Rank – Adapt It gives estimate of development effort – Client commit to proposed cost for development • Cost the fixed element The Alternative? • Proposal: Alternative development route (continue) – Development start with REGULAR feedback (sprint reviews) • Discuss specification or show functioning software • Adapt IT log hours for sprint period – Client SEE what time is spend on • Client can make comments (communication) • Not a Prototype The Alternative? • Proposal: Alternative development route (continue) • If there are changes in requirement: – Adapt It add new things or make changes – This might mean that the scope will not be delivered » In time » With all the features The Alternative? • Proposal: Alternative development route (continue) – When committed amount is used up • Declare satisfaction with features delivered or • Negotiate additional funds • Client will have functioning software How will this be done in practice? • Waterfall How will this be done in practice? • Agile How will this be done in practice? • Agile Challenges to follow the Alternative route • Adapt IT: – – – – – Must have regular reviews Must log and share time for sprint period Must be agile enough to adapt development path Invoice on different basis Overcome the communication barrier via electronic means (WebEx) • Client: – Must be available for review – Need to accept the move away • From contract • To value delivery in shorter period Conclusion • I believe that the quality of software can be better through effective communication – In the code because we have better knowledge of the business domain – And the applicability of the software • My message is that we need to take a step forward in doing things differently to achieve this. • I wish that none of you will experience a pain between the eyes because of unknown elements Disclaimer • The information, comments and material presented in this presentation are provided for information purposes only. The presentation is not addressing all possible technical or business aspects and does not claim to be complete or exhaustive. • Adapt IT reserves the right to change its business or product development plans as circumstances dictate. • This document may not be reproduced or distributed without the written permission of Adapt IT (Pty) Ltd. Questions? Thank you.
