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

Manage IT by Johanna Rothman

I just completed this book. I think it is a really good book which covers a whole lot of software development. This book could possibly be the best book for first time project managers. I believe many of the PMs understand PMM but do not understand software development. This book gives a view of each project role. The only one that it does not cover is Business Analyst or requirements documentation. It does cover QC, development and of course PMs. It gives a PM a view into development processes like TDD, CI and estimation. Many PMs that are new to SD can read this book and get a great start to manager an SD project. If you are a PM or know some, read this book. http://www.jrothman.com/
3 comments
Read more

Matrix Organizations are bad for Software Dev

Development teams need to be teams first and company people second. What happens when your team wants to start using user stories and index cards, but your analyst team manager thinks Use Cases are the best way to document requirements? How about when your QA process is not mature and you keep releasing with defects but the QA manager does not do anything about it? How about your project manager never buys into the team and only cares about being on time and on budget because their review is based on it. Maybe the tech lead wants requirements that never change and never lets the client change their mind. The technical manager taught your tech lead and agrees with everything the tech lead says. Agile or what I like to call "Successful Teams" are teams. They do what it takes to do what the customer wants, deliver features. I am not saying only agile teams are successful but successful teams are agile. If your organization is matrix, get your leadership buy in to override...
3 comments
Read more