You must be logged in to update your preferences.
As Comic-Con San Diego nears, I thought I would share this little vignette from the recent Emerald City Comic-Con. My Close Encounter with Stan Lee My Emerald City Comic-Con hook up was running late. So rather than stand around the all too crowded, and under-seated lobby of the Washington State Convention Center, I walked across …
The post My Close Encounter with Stan Lee appeared first on Serious Insights.
This much should be obvious: You can’t plan to have everyone occupied 100% of their time on fixed-date work, allow them to be interrupted by expedited items, and still expect predictability.
The role of the Enterprise Architect is fundamental in assuring that projects are scoped correctly and that they deliver on their promise (deliver the right context). Will Enterprise Architecture save US companies US$80M a year in failed I IT projects? (See CHAOS Manifesto), and what are the key characteristics of the Enterprise Architect that will stop 30% of my IT projects failing?
How many organisations have you come across with a heart? And with a soul? Personally, it’s been precious few. Yet for those rare encounters, it’s a palpable joy, isn’t it? Precious indeed.
It’s important to remember that the result that we’re working toward is a working kanban system, not a static model. It’s best not to get too attached to the products of this exercise—they will quickly lose their value once the system begins to evolve.
I’ll keep this simple by assuming that there is just one main workflow involved. If you have more than one, you can take each workflow in turn or use one as the baseline by which the others are described.
It’s about time I posted the notes I email to people who ask about facilitating Featureban, so here goes…
This report outlines ten areas of technology innovation led by a variety of vendors. None of the areas mentioned here have become fully realized, nor do any of them currently dominate the requirements of organizations seeking to acquire or shift their collaboration platforms.
Last week I attended Salesforce’s Connections “World Tour” in New York. As I have attended nearly a dozen such user conferences over the last three months, I feel well-qualified to say that the company’s customers are some of the fiercest networkers I have ever met.
We’re two chapters into Part III and getting into the nitty-gritty of Kanban implementation using the STATIK model. This week’s excerpt comes from the chapter introduction.
The previous chapter was all about context and perceptions, mostly keeping implementation considerations off the table. This chapter is about gathering some specific qualitative and quantitative facts about the current process that will inform the design of kanban systems.
This is part 6 of an on-going series on the history of omni-channel. Part 1 addressed the point when customer centricity and “cross-channel” (the early days of omni-channel) first merged and became the foundation of what most people mean when they say omni-channel today.