Skip to main content

KanBan for Operations and maybe for Development

We have been working on a solution to gain better control of our operations work and projects.  With Windows 2003 expiring in July, we have been out of control or not focused.  We have adopted KanBan.  Why, because it just felt right.  No real reason or specific goal but just thought a system that appeared to keep people focused and had an easy way to track the work.


I found the pod cast below really helped to solidify my thoughts on KanBan and why it is a great tool for operations work.  Instead of my repeating why it is needed, just listen to the Pod Cast and by the way, their other Pod Cast are really good too.


http://www.cloudtp.com/2015/01/13/kanban-scrub-devops/


Another great tool we are using is KanBanTool.com.  Do you have to use it, no?  You can use sticky notes and index cards.  Some of the people on my team are managing their time with sticky notes with a BackLog, WIP and done KanBan approach.


KanBan for development might be another animal.  They make it clear that KanBan requires more trust from the client.  I can see it working well if you are doing small feature based or bug fix work because they are just sitting in a queue waiting to be done and flexible delivery times.


Just some quick thoughts....

Comments

Post a Comment

Popular posts from this blog

2020 State of DevSecOps by Accurics

 This is an excellent report for all IT Pros and Engineers.   Highlights: Storage is most impacted solution Open security groups or network configuration Secrets are not so secret Unused resources are not secure. Take a look at these.  Look again.  These are not highly skilled problems.  They just need guidelines and proactive management.  The article uses policy as code as a solution for many of the problems.  I will drill into each of these more in the future.  I wanted to get the awareness out first and then, come back to solutions.  
Post a Comment
Read more

Learn Anti-Leadership from Basecamp

 There are many different articles out there and Twitter comments about the Basecamp drama.  I am not going to post any here because it might seem biased depending on the article.  Google them yourself.  In short, Basecamp made a policy to not allow political discussions at work.  Coinbase did this previously too and applauded Basecamp for it.   Apparently, for years there has been a list of funny customer names at floating around Basecamp.  This list or even the knowledge that Basecamp had a list, was disturbing to some employees.  Also, some employees tried to start a Diversity and Inclusion practice.  Despite how much the founders of Basecamp promoted DI, they didn't feel they were being taken serious.  They felt the company was only about the founders and not about employees.    If this isn't enough, the founders debated and even called out employees for their comments regarding the topics, publicly.  This is my s...
Post a Comment
Read more

Cloud Ops: The New IT for the Cloud Era

Over the past few months of interviewing and researching dozens of companies—particularly small to mid-sized SaaS businesses—one pattern keeps emerging: the desire to stand up a Cloud Operations (Cloud Ops) organization. It makes sense on the surface. Cloud is now the infrastructure of choice, so naturally, someone needs to “own” it. But what’s unfolding in practice often misses the mark. Many companies are attempting to solve growing cloud complexity by taking all their DevOps, SRE, and platform engineering talent and consolidating them into a Cloud Ops team. The idea? Share them across product teams so no one gets overwhelmed. If that sounds familiar, it should. It’s the same centralization tactic used by traditional IT for decades. And it's creating the same problems. When Cloud Ops Becomes Old IT in Disguise Here’s the playbook we’re seeing: Move DevOps, SRE, and Ops into a central Cloud Ops team. Let them handle infrastructure, CI/CD, monitoring, and cloud securit...
Post a Comment
Read more