Book contents
- Frontmatter
- Dedication
- Contents
- Figures
- Tables
- Foreword
- Preface
- Acknowledgements
- Overview of the Book
- 1 Knowledge Driven Development: What is the Proposition?
- 2 Project Delivery and Supporting Methodologies
- 3 Project Delivery Pain Areas and the Way Forward
- 4 Project Knowledge Model: Context and Definition
- 5 Project Knowledge Model: A Differentiator
- 6 Project Knowledge Model vs Project Documents
- 7 Extending Project Knowledge Model to Cover End-to-End Project Delivery – KDD
- 8 Extended KDD: Pre-Requirement and Post Delivery
- 9 KDD Compliance with Standards of Project Delivery
- 10 Enabling DevOps
- 11 Addressing Contemporary Concerns of Project Delivery
- 12 Helping Existing Methodologies
- 13 Technology Enablers: Tools and Automation
- 14 Suits Factory Model: Needs Cultural Change
- 15 Global Relevance of KDD: GKMF Assisting Skill Development
- 16 Lean KDD: Elimination of Requirement and Test Design?
- 17 Conclusion
- Appendix A Illustrative Non-Functional Attributes
- Appendix B Compliance of PKM with GKMF
- Appendix C Project Estimate and Business Rule/Scenario Framework
- Appendix D Inventory Relationship for Setting up of Security Questions – as per Example in Chapter 6
- Appendix E KDD: Response to Criticism
- Glossary
- References
- Index
Overview of the Book
Published online by Cambridge University Press: 20 October 2018
- Frontmatter
- Dedication
- Contents
- Figures
- Tables
- Foreword
- Preface
- Acknowledgements
- Overview of the Book
- 1 Knowledge Driven Development: What is the Proposition?
- 2 Project Delivery and Supporting Methodologies
- 3 Project Delivery Pain Areas and the Way Forward
- 4 Project Knowledge Model: Context and Definition
- 5 Project Knowledge Model: A Differentiator
- 6 Project Knowledge Model vs Project Documents
- 7 Extending Project Knowledge Model to Cover End-to-End Project Delivery – KDD
- 8 Extended KDD: Pre-Requirement and Post Delivery
- 9 KDD Compliance with Standards of Project Delivery
- 10 Enabling DevOps
- 11 Addressing Contemporary Concerns of Project Delivery
- 12 Helping Existing Methodologies
- 13 Technology Enablers: Tools and Automation
- 14 Suits Factory Model: Needs Cultural Change
- 15 Global Relevance of KDD: GKMF Assisting Skill Development
- 16 Lean KDD: Elimination of Requirement and Test Design?
- 17 Conclusion
- Appendix A Illustrative Non-Functional Attributes
- Appendix B Compliance of PKM with GKMF
- Appendix C Project Estimate and Business Rule/Scenario Framework
- Appendix D Inventory Relationship for Setting up of Security Questions – as per Example in Chapter 6
- Appendix E KDD: Response to Criticism
- Glossary
- References
- Index
Summary
Generally, there are two types of people in the world: one who follow processes and methodologies as written in books, and the other who enjoy breaking rules and doing things differently. The latter can also be split into two categories: those with good intentions and those with bad intentions. The first category produces innovation and the second category produces criminal behaviour. Society has all these kinds of people. In a healthy society, a majority of people follow processes, some have honourable intentions in breaking rules and only a very few have criminal intentions.
This is evident in software project delivery as well. Let's see how it happens there. Almost all projects select a project delivery methodology (there are many to choose from). There will be a set of people in the project who will understand the intent of the methodology and try to follow it while performing their assigned tasks. There will be another set of people who will have the maturity to understand that certain portions of the project delivery can be better accomplished by slightly tweaking the methodology steps and they will propose this to their colleagues. There will also be a few people who, for less honest reasons, will argue against the methodology steps or suggestions for change. They might propose something that will make their task easier, even if it becomes difficult for the majority of the team to accommodate their proposal. They will take excuses of someone's failure and justify delays from their side. They will create an opaque boundary around their work so that the transparency in the project progress is hindered.
While there may be a majority of people falling under type one (process followers), there are significant number of people falling under the second type, category one (rule breakers with good intentions) and category two (rule breakers with bad or selfish intentions). A fine balance between all these types of people needs to be maintained by the project management. That is why success and failure of a project today is largely in the hands of the project manager, even if the team is highly skilled and experienced.
Depending only on the project management to drive a project is not the best solution. The industry is keen to solve this issue at a strategic level. A major roadblock is that the IT industry is still knowledge-intensive.
- Type
- Chapter
- Information
- Knowledge Driven DevelopmentBridging Waterfall and Agile Methodologies, pp. xxv - xxxPublisher: Cambridge University PressPrint publication year: 2018