Showing posts with label kaizen. Show all posts
Showing posts with label kaizen. Show all posts

Monday, June 17, 2019

How to Make Continuous Delivery a Reality in an Agile Environment

Continuous integration and continuous delivery (CI/CD) are core elements of successful DevOps. Systems engineers may start with CI because it is familiar. With a DevOps focus, organizations uncover configuration, packaging, and orchestration that are necessary to effective software development life cycle (SDLC). This empowers developers, administrators and engineers to create valuable CD practices, adding to agility.

Where less experienced developers might struggle with CI/CD performance, testing delays and other bottlenecks, the enterprise would do well to develop processes and best practices to make DevOps in the cloud a value-driven methodology. To save money, this will shorten the SDLC — because CD is all about updating web services. In public clouds such as AWS and Azure, this is done through pipeline stages (e.g. dev, test, staging and production). When containers are implemented with a platform-as-a-service (PAAS) approach, stages become sandbox environments, scratch instances, and production instances.

The benefit of such an approach is that the work outputs and products themselves benefit from flexibility. Regular face-to-face interactions and collaborations between team members are conducted to ensure the scrum teams level-set expectations. Finally, add value by continuous delivery throughout the life cycle, so that the end product is more secure and more reliable. Implementing an agile manifesto tracks with addressing evolving end user requirements. 

For CD, ensure user stories are married correctly to those requirements and that each story rolls up to an Epic that represents a standalone feature. This enables the devops team to release reasonably sized components of functionality that are consumable by users. These are also traceable back to the release plan. We want to ensure verification at each stage because this process defines acceptance criteria — so the stakeholders know when something is declared “finished.”

Schema, user interface, access control rights and static resources such as icons and images are all part of the creation process and we manage them just as diligently as source code. The DevOps team checks assets into a version control system as a single source of truth (GIT or Subversion). This benefits the client by ensuring that developers are making changes in a segregated environment — catastrophic failures are completely avoided with such approach, and integration into a risk management-based security framework is seamless. 


The organization should understand automated quality processes are essential — Selenium is a go-to tool for testing functionality. There are several verifications to make before functional testing. Static code analysis tools, such as PMD, are essential to ensure code conforms to a single style. Unit test coverage is also essential — establish a set of Key Performance Inidcators (KPIs) for coverage of at least 75% of code. Finally, after these automated tests pass, implement a manual peer review. This enables seasoned developers  to spot opportunities for performance improvement where automated tools can’t.

Sunday, August 23, 2015

Using Process Improvement to Delivery Relief - from Toyota to NYC

Kaizen is all about process improvement. Toyota brought their knowledge of supply chain management to relief efforts in New York City after Hurricane Sandy. The benefits of Toyota Production System in nonprofits is clear: smooth operations, lowered cost, faster turn-around. Non-profit organizations are experiencing increasing client demand, making operational improvements critical to growth and success. Particularly in the food bank arena, issues of timely deliveries to partner agencies mirror warehousing and logistic issues in other industries, making the Toyota Production System (TPS) philosophy and lean principles applicable to this setting.

Watch the video here...

Monday, October 21, 2013

Apple's Steve Jobs was too quick to tie the knot with Microsoft, and Google

Around the 2nd anniversary of his death, and looking back at Steve Jobs’ tenure at Apple, it iss impossible to separate the role Microsoft and Bill Gates played in SJ's complex career. Microsoft and Apple helped pioneer the personal computing industry and defined not one, but two eras (PCs, and the post-PC mobile world). The two CEOs partnered at various times, competed all the time, and challenged one another in ways that helped shape the landscape of technology.

Early on, the strength of their relationship could be witnessed at an Internal Apple Event in Hawai where Steve Jobs introduced the Macintosh to a few Apple VIPs. Bill Gates sugarcoated the Mac and Steve Jobs loved every moment of it.

But with Bill Gates famously ripping off the Mac interface, a rift was formed.

This was somewhat healed, over time, when Steve returned to save Apple, and even, to the dismay of Apple loyalists, called on MS to help. In the new era of cooperation caused by intense competition from all corners of the Internet, Steve brought Google into the fold early. And this was a mistake as big as handing the Mac prototype to Bill Gates.

Rob Enderle, at Forbes, convenes a moot court to try and convict Google,
The fact that Google copies isn’t in dispute. They clearly have copied Microsoft and really there is nothing wrong with that other than trying to argue the efforts (other than price) are innovative. The sequence of events suggest that someone got the idea of doing a phone before Apple locked down on the iPhone, but after the ROKR, and were unsure as to what to create. That was until the iPhone emerged at Apple and then they created a very similar, though initially inferior product. So we have historical behavior that showcases Google copies, we have motive (to build a better phone), and with Schmidt on the board we have opportunity.

Broadly, Google (and Samsung and others) clearly did “steal” Apple’s technology. A number of key concepts, such as pinch-to-zoom, were first introduced on the iPhone and later incorporated into Android. The iPhone was an innovative product, and obviously Apple’s competitors are going to want to match it feature for feature. This is a good thing, for consumers. Better products all around, and more choice.

But Steve Jobs, for all his reputation as a tough leader, also followed his heart. Of the many qualities made Steve Jobs an innovator, one key aspect was his interest in Zen Buddhism. He relentlessly filtered out what he considered distractions (focusing the mind)and his passion for taking responsibility for every element of a product reflect a Zen approach. Not controlling, but responsibility, a core concept of the experience. Read more about the influence of this way of thought on Steve Jobs. Sometimes mistakes are opportunities for growth.


Monday, January 28, 2013

I never thought I'd See This: Consultants are, gasp, Good?!

In a recent Slate article, we read that management consultants are actually a boon to business!

A recent experiment by World Bank and Stanford researchers illustrate the dramatic impact of management “technology” on the way companies are run. The researchers randomly assigned a management makeover to a handful of Indian textile firms, while at the same time following a set of control textile factories to benchmark the effects of good management.
Out of chaos, order arose: Supply closets were no longer strewn about with yarn, factory floors were cleaned up, inventory and control processes improved production line efficiency. The benefits of good management were such that Accenture’s services—which were provided to the companies for free as part of the experiment—would have paid for themselves through greater profitability within a year: The researchers estimated a profit increase of more than $300,000 annually as a result of management improvements, as compared with the $250,000 market price of the consulting services they received.
What brought about these changes? Exactly the sorts of things that the managers of Davos are good at: designing incentives, ensuring clear and well-defined assignments of tasks and responsibilities, putting in place protocols to manage and track inventory and production. These are not new ideas. They have been the standard protocols of much-maligned managers since they first appeared on the scene with the advent of transcontinental railroad. It’s just that management, despite its age, is not evenly distributed around the world.


Slate's assertion: Better management stands a far greater likelihood of making the world wealthier and healthier. And that's a good thing.


- Posted by Tom/Bluedog

Sunday, January 20, 2013

High Tech Projects can have Serious Complexity Issues

Boeing is the leader in air craft manufacturing, and the Dreamliner is characterized as the most advanced, best performing and most comfortable passenger plane to date. The approach the company took in the design and building of the plane is just as revolutionary.

Boeing took a radical approach to working with many suppliers -- 787 development and production involved a large-scale collaboration with numerous suppliers around the world. The manufacturer assigned the global subcontractors to do as much assembly themselves as practical, and deliver completed subassemblies to Boeing for final construction. The intent was to have a leaner assembly line and lower inventory, with pre-installed systems reducing final assembly time by as much as three days.

The aircraft was designed to become the first production composite airliner, with its fuselage assembled in one-piece composite tubular sections instead of multiple aluminum sheets, the approach used on most modern aircraft. Its "fly-by-wire" approach is the most extensive implemented, outside of the U.S. military.

But, as with many complex technological undertakings, problems materialize, sometimes even after the project is stamped "done" by management. In fact, with the case of the Dreamliner, serious concerns have arisen regarding electrical problems. And, with an aircraft, such problems translate into the safety of passengers, crew and others. Human life is at stake when 200+ people are traveling at subsonic speeds. So, caution is always called for, as the recent grounding of All Nippon Airway's fleet of Dreamliners shows.

What can information technology professionals learn from this on-going story? In the past, all products were handmade, the work of artisans rather than manufacturers. Cars, clocks, and firearms, for example, started out as being made one at a time, and each iteration was subtly different than the one the craftsmen finished just the day before. Over time industry has learned the value of standardized, interchangeable parts, and ultimately, about mass production. Even "mass customization." Though the retro movement highlights handiwork, for most products, systematic production yields far better products at much lower costs.

This FastCompany article discusses how NASA makes their onboard shuttle software. Take a look at NASA's checklist (PDF) to see how 100% defect free is necessary when lives are on the line.

Tuesday, October 16, 2012

Lanthanum? Unubtanium? What's the Most Valuable Resource.

As readers may have come to realize, my position on the most valued commodity is, in fact, not a commodity at all. I see knowledge workers as the key to success, at the micro-economic level (talented staff, discerning customers), and, as The Economist reports, at the macro level:

THE world’s most valuable resource is talent. No country grows enough of it. Some, however, enjoy the colossal advantage of being able to import it. Rich, peaceful countries can attract clever immigrants. Unlike other useful imports, they cost the recipient country nothing. They come, they study, they work, they set up businesses, they create jobs: 40% of the founders of Fortune 500 companies are immigrants and their children. Yet they are only 23% of Americans.


I've consistently advocated for immigration, both in the U.S. and in the Republic of Ireland, as the secret sauce to boost entrepreneurialism. My grandfather arrived illegally in New York, and made his way to being a successful baker, in spite being an "enemy of the state" during the 2nd World War. He, like many others, chose to be American (nobody chooses their heritage/nationality) -- the hallmark of civilized human rights is the freedom to migrate. And these two countries remain magnets for the talented, the motivated, the (learned or not) quick-witted.





- Posted by Tom/Bluedog

Friday, July 13, 2012

Finally, a Serious Contender for the School Run

Ask my kids -- I am king of the school run drift. There's no thrill quite like beating the big yellow bus to the car park, with time to nosh a breakfast treat at the Parkway Deli. Alas, the days of the Supra or AE86 seem to be in the past. Or are they? With the advent of modern sports cars, Toyota's president (and grandson of the company founder), Akio Toyoda, surely asked himself, “Where is the passion in our lineup? I want to build a sports car.” The all-new Scion FR-S is just such a car, and is available in June 2012. This graph shows the specs and the evolution of the car from predecessor Toyota models. Inspired by rear-drive Corolla of the ’80s that became the darling of drifters, this new sports car is light, agile, and affordable.
Delia, Damon and Jason will certainly concur -- Scion has succeeded in making the FR-S agile. From the quick steering to the responsive chassis, the FR-S responds to driver input in a way that reminds me of rear-wheel drive sports sedans of yore. Depress the stability control button for three seconds and things liven up even more. Although the chassis is neutral, it will slide appreciably with the right inputs. In my opinion, suspension, steering and power in the FR-S works with harmony. The stock tyros allows for accessible explorations of the FR-S’s behavior at the edge of the envelope -- the sort of exploration that makes getting to school in the morning fun.

Tuesday, May 1, 2012

How ERP and Lean Can Work Together

Enterprise resource planning software is the lynchpin in corralling and centralizing important data in a business's transaction processing. The role of manufacturing and distribution software in supply chain management solutions is growing in impact as businesses attempt to respond faster to market conditions during these difficult economic times. I've been reviewing offerings from TGI (http://www.tgiltd.com/) that could be a radical step forward, when paired with Lean Production. Lean manufacturing aims to eliminate components and processes, whether that is excess stock, inventory, excess parts or handling, or labor. Using ERP software automation to improve operational efficiency makes perfect sense when implementing process improvement. What I've witnessed is that, for Japanese companies, ERP software is more prevalent at the top of a lean process, especially in industries such as car manufacturing (Honda) or consumer electronics (Sony). Japanese companies are less likely to face the need to rebuild ERP software or even MRP systems to support new manufacturing techniques -- something businesses world-wide could emulate to find cost savings and other efficiencies.

Tuesday, March 13, 2012

Learning from Japan


Disaster response is baked into the Japanese psyche, as we can see from the amazing post-melt-down, post-tsunami reports on the anniversary.

But Japan has a whole lot more to offer, including how a society can be polite without a top-down command-structure, and how to continuously improve, in business and personally.

Of course, the onsen is one of my favorites, and why hasn't the world adopted the Toto toilet wholesale?

Read more here at Michael Todd's...