|By Tad Anderson||
|August 1, 2014 08:15 AM EDT||
Processes are not documented and reused by a set of individuals because they lead to failure. Like design patterns, they are documented and reused because they lead to success.
They are all put together by very talented people who have successfully used them to develop software multiple times. For them the process is easy to use and understand. The teams that have not used it have a steep learning curve ahead of them. Just looking at the diagram of a pattern or process, definitely will lead you to failure every time.
I have seen Waterfall, Spiral, RUP, OpenUP, and Scrum all fail multiple times each because project managers, architects, developers, CIOs, and IT managers have only gone as far as looking at the diagram of the process they choose to use. They apply practices and principles they already know to the models instead of the ones that go with the models. The principles and practices that are behind the model must be learned and used in order to succeed.
|I assume this is a trick insanity plays on them. Doing the same thing over and over again expecting a different result. They thought renaming and reordering what they already do was actually changing.
This book is required reading if you want to understand the Incremental Commitment Spiral Model (ICSM) and it's related diagrams. If you are not going to read the book, please do not attempt to use the diagram. After a very nice introduction it is broken down into five parts including the afterword. I have list each part and the chapters it includes below.
Part I: The Four ICSM Principles
1. The First Principle: Stakeholder Value-Based Guidance
2. The Second Principle: Incremental Commitment and Accountability
3. The Third Principle: Concurrent Multidiscipline Engineering
4. The Fourth Principle: Evidence- and Risk-Based Decisions
Part II: ICSM Life Cycle and Stage I: Incremental Definition
5. The ICSM Life Cycle
6. Exploration Phase
7. Valuation Phase
8. Foundations Phase
Part III: Stage II: Incremental Development and Evolution
9. Development Phase
10. System Production and Operations
Part IV: Applying ICSM to Your Organization
11. ICSM Patterns and Common Cases
12. ICSM and Your Organization
13. Evidence-Based Life-Cycle Management
14. Cost and Schedule Evidence Development
15. Risk–Opportunity Assessment and Control
Appendix A. Evidence Evaluation Framework
Appendix B. Mapping between ICSM and Other Standards
Appendix C. A Value-Based Theory of Systems Engineering
Don't make the mistake of looking at this book and saying "oh, it's that old model again", it's not the 1988 spiral model- A Spiral Model of Software Development and Enhancement. The 1988 spiral model began the long process leading to the spiral model in this book, the Incremental Commitment Spiral Model (ICSM).
Developing software correctly is easy. The hard part is having all the skills needed to do that. Since most teams do not possess the skills needed to easily execute a software development process, they usually have a hard time. Even those who gave it their best shot learning the practices and principles behind the 1988 model had a hard time succeeding.
Within a short time the feedback that reached Dr. Boehm lead him to claim "What we really need are process model generators". I agree 100%. Implementing a development process instance for a given project is the only way to correctly use software development processes. Just as important, if not more important, is the ability to understand what is happening with your project and to change the process as needed. Teams seem to have a much harder time with that. Luckily that is what we got with this book.
Software process engineering allows you to account for your team's skills and availability, your businesses needs, the tools you have available, the environment you are working in, the difficulty of the solution, the working environment - team member locations, greenfield vs. brownfield development, and many more things that are usually not taken into consideration at all. Software process engineering not only gives you the instance to work with, it also allows for tailoring the process to meet the needs of the project as circumstances change throughout the project.
People leave, laws changes, hurricanes happen (although that didn't stop us- dumb, dumb, dumb), people get sick, and so on. The point is your process must be as agile and resilient as your software. That means the process must be changeable.
I have sat in a room watching project managers and business users debate for hours about what to do now that they have discovered the next 3 sprints will take 3-4 weeks and not the 2 weeks they had agreed on.
1/2 of them wanted to split functionality (user stories) to meet the 2 week mark and add it back later with 3 more sprints but that would really mean 4 extra sprints because splitting the functionality adds complexity to the programming. Some of them wanted to borrow a few developers, while others just wanted to pretend they didn't know and just start the next 2 weeks after they got done this sprint. No deliverables or tests, just keep going and hope they weren't questioned. All of this is non-transparent nonsense, and is anything but agile.
This book is not a software development process. The author's say "The ICSM is not a single, one-size-fits-all process. It is actually a process generator…". The book did not meet my expectation of what that means to me. In order for it to be a process generator, it would need to reference one or more specific process asset repositories which can be configured into an instance of a process.
That does not detract from the value of the book, because we already have enough process asset repositories. My perception of the content of the book is that it is material that will help you audit, adjust, and manage a software process. That is needed more in today's industry. The rest of the sentence that begins the paragraph above is consistent with my understanding of the book's content- "… that steers your process in different directions, depending on your particular circumstances."
One very cool thing about this book is that the material is available online. The material has been published from Eclipse Process Framework. At least it looks like it to me. There are two sites, The Incremental Commitment Spiral Model (ICSM) and The Instructional Incremental Commitment Spiral Model (ICSM) Electronic Process Guide. The Instructional Incremental Commitment Spiral Model (ICSM) Electronic Process Guide is a version of ICSM which is tailored to fit the nature of CSCI577ab Software Engineering Class.
The one thing that drove me kind of nuts while reading this book is the very heavy use of acronyms. They probably drove me crazy because they brought back flashbacks of being in the Army and working for the State of PA.
The thing I liked most about this book is the honesty found in it. An example is found in the first paragraph of the Preface- "Rumor has it, however, that some people would rather deliver an unsuccessful system so that they can continue being paid to make it successful; rumor also doubts those people will read this book." They also present failure stories for each success story, which really helps to keep the book grounded in reality.
All in all I found this book an excellent read. It contains a ton of wisdom gathered over a very long period of time.
The Incremental Commitment Spiral Model: Principles and Practices for Successful Systems and Software
The Incremental Commitment Spiral Model: Principles and Practices for Successful Systems and Software
The Internet of Things (IoT) is growing rapidly by extending current technologies, products and networks. By 2020, Cisco estimates there will be 50 billion connected devices. Gartner has forecast revenues of over $300 billion, just to IoT suppliers. Now is the time to figure out how you’ll make money – not just create innovative products. With hundreds of new products and companies jumping into the IoT fray every month, there’s no shortage of innovation. Despite this, McKinsey/VisionMobile data...
Nov. 25, 2015 10:00 AM EST Reads: 424
One of the most important tenets of digital transformation is that it’s customer-driven. In fact, the only reason technology is involved at all is because today’s customers demand technology-based interactions with the companies they do business with. It’s no surprise, therefore, that we at Intellyx agree with Patrick Maes, CTO, ANZ Bank, when he said, “the fundamental element in digital transformation is extreme customer centricity.” So true – but note the insightful twist that Maes adde...
Nov. 25, 2015 09:00 AM EST Reads: 394
Just over a week ago I received a long and loud sustained applause for a presentation I delivered at this year’s Cloud Expo in Santa Clara. I was extremely pleased with the turnout and had some very good conversations with many of the attendees. Over the next few days I had many more meaningful conversations and was not only happy with the results but also learned a few new things. Here is everything I learned in those three days distilled into three short points.
Nov. 25, 2015 09:00 AM EST Reads: 263
Nov. 25, 2015 08:30 AM EST Reads: 139
As organizations realize the scope of the Internet of Things, gaining key insights from Big Data, through the use of advanced analytics, becomes crucial. However, IoT also creates the need for petabyte scale storage of data from millions of devices. A new type of Storage is required which seamlessly integrates robust data analytics with massive scale. These storage systems will act as “smart systems” provide in-place analytics that speed discovery and enable businesses to quickly derive meaningf...
Nov. 25, 2015 08:15 AM EST Reads: 342
DevOps is about increasing efficiency, but nothing is more inefficient than building the same application twice. However, this is a routine occurrence with enterprise applications that need both a rich desktop web interface and strong mobile support. With recent technological advances from Isomorphic Software and others, rich desktop and tuned mobile experiences can now be created with a single codebase – without compromising functionality, performance or usability. In his session at DevOps Su...
Nov. 25, 2015 07:45 AM EST Reads: 340
You may have heard about the pets vs. cattle discussion – a reference to the way application servers are deployed in the cloud native world. If an application server goes down it can simply be dropped from the mix and a new server added in its place. The practice so far has mostly been applied to application deployments. Management software on the other hand is treated in a very special manner. Dedicated resources are set aside to run the management software components and several alerting syst...
Nov. 25, 2015 07:30 AM EST Reads: 121
In his General Session at DevOps Summit, Asaf Yigal, Co-Founder & VP of Product at Logz.io, explored the value of Kibana 4 for log analysis and provided a hands-on tutorial on how to set up Kibana 4 and get the most out of Apache log files. He examined three use cases: IT operations, business intelligence, and security and compliance. Asaf Yigal is co-founder and VP of Product at log analytics software company Logz.io. In the past, he was co-founder of social-trading platform Currensee, which...
Nov. 25, 2015 06:45 AM EST
It's been a busy time for tech's ongoing infatuation with containers. Amazon just announced EC2 Container Registry to simply container management. The new Azure container service taps into Microsoft's partnership with Docker and Mesosphere. You know when there's a standard for containers on the table there's money on the table, too. Everyone is talking containers because they reduce a ton of development-related challenges and make it much easier to move across production and testing environm...
Nov. 25, 2015 04:00 AM EST Reads: 549
People want to get going with DevOps or Continuous Delivery, but need a place to start. Others are already on their way, but need some validation of their choices. A few months ago, I published the first volume of DevOps and Continuous Delivery reference architectures which has now been viewed over 50,000 times on SlideShare (it's free to download...no registration required). Three things helped people in the deck: (1) the reference architectures, (2) links to the sources for each architectur...
Nov. 25, 2015 02:30 AM EST Reads: 195
Continuous processes around the development and deployment of applications are both impacted by -- and a benefit to -- the Internet of Things trend. To help better understand the relationship between DevOps and a plethora of new end-devices and data please welcome Gary Gruver, consultant, author and a former IT executive who has led many large-scale IT transformation projects, and John Jeremiah, Technology Evangelist at Hewlett Packard Enterprise (HPE), on Twitter at @j_jeremiah. The discussion...
Nov. 25, 2015 02:30 AM EST Reads: 681
Hiring the wrong candidate can cost a company hundreds of thousands of dollars, and result in lost profit and productivity during the search for a replacement. In fact, the Harvard Business Review has found that as much as 80 percent of turnover is caused by bad hiring decisions. But when your organization has implemented DevOps, the job is about more than just technical chops. It’s also about core behaviors: how they work with others, how they make decisions, and how those decisions translate t...
Nov. 25, 2015 12:45 AM EST Reads: 135
In today's enterprise, digital transformation represents organizational change even more so than technology change, as customer preferences and behavior drive end-to-end transformation across lines of business as well as IT. To capitalize on the ubiquitous disruption driving this transformation, companies must be able to innovate at an increasingly rapid pace. Traditional approaches for driving innovation are now woefully inadequate for keeping up with the breadth of disruption and change facin...
Nov. 25, 2015 12:30 AM EST Reads: 417
The Internet of Things is clearly many things: data collection and analytics, wearables, Smart Grids and Smart Cities, the Industrial Internet, and more. Cool platforms like Arduino, Raspberry Pi, Intel's Galileo and Edison, and a diverse world of sensors are making the IoT a great toy box for developers in all these areas. In this Power Panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, panelists discussed what things are the most important, which will have the most profound...
Nov. 25, 2015 12:30 AM EST Reads: 410
PubNub has announced the release of BLOCKS, a set of customizable microservices that give developers a simple way to add code and deploy features for realtime apps.PubNub BLOCKS executes business logic directly on the data streaming through PubNub’s network without splitting it off to an intermediary server controlled by the customer. This revolutionary approach streamlines app development, reduces endpoint-to-endpoint latency, and allows apps to better leverage the enormous scalability of PubNu...
Nov. 24, 2015 10:00 PM EST Reads: 259
I recently attended and was a speaker at the 4th International Internet of @ThingsExpo at the Santa Clara Convention Center. I also had the opportunity to attend this event last year and I wrote a blog from that show talking about how the “Enterprise Impact of IoT” was a key theme of last year’s show. I was curious to see if the same theme would still resonate 365 days later and what, if any, changes I would see in the content presented.
Nov. 24, 2015 08:00 PM EST Reads: 342
Microservices are a very exciting architectural approach that many organizations are looking to as a way to accelerate innovation. Microservices promise to allow teams to move away from monolithic "ball of mud" systems, but the reality is that, in the vast majority of organizations, different projects and technologies will continue to be developed at different speeds. How to handle the dependencies between these disparate systems with different iteration cycles? Consider the "canoncial problem"...
Nov. 24, 2015 06:00 PM EST Reads: 370
Culture is the most important ingredient of DevOps. The challenge for most organizations is defining and communicating a vision of beneficial DevOps culture for their organizations, and then facilitating the changes needed to achieve that. Often this comes down to an ability to provide true leadership. As a CIO, are your direct reports IT managers or are they IT leaders? The hard truth is that many IT managers have risen through the ranks based on their technical skills, not their leadership ab...
Nov. 24, 2015 06:00 PM EST Reads: 321
Discussions of cloud computing have evolved in recent years from a focus on specific types of cloud, to a world of hybrid cloud, and to a world dominated by the APIs that make today's multi-cloud environments and hybrid clouds possible. In this Power Panel at 17th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the importance of customers being able to use the specific technologies they need, through environments and ecosystems that expose their APIs to make true ...
Nov. 24, 2015 03:30 PM EST Reads: 462
There are over 120 breakout sessions in all, with Keynotes, General Sessions, and Power Panels adding to three days of incredibly rich presentations and content. Join @ThingsExpo conference chair Roger Strukhoff (@IoT2040), June 7-9, 2016 in New York City, for three days of intense 'Internet of Things' discussion and focus, including Big Data's indespensable role in IoT, Smart Grids and Industrial Internet of Things, Wearables and Consumer IoT, as well as (new) IoT's use in Vertical Markets.
Nov. 24, 2015 03:30 PM EST Reads: 510