Recently my team was tasked with changing the default VxLAN port, used by OpenShift to create SDN networks for the individual namespace (Project). Problem was, that we needed to do it on a running cluster, with no downtime.
Why would you ever want to do something like that?! Well… we really did not want to do that. We were however forced by VmWares, highly questionable, implementation of VxLAN in there NSX product.
When writing scripts for Jenkins pipelines for our different development teams using our OpenShift platform we found that maintaining individual Jenkinsfiles for each project quickly gets messy. Surprise!
#Simple lib file for jenkins functions - and how to load it
Our current solutions is to create a general purpose Groovy file with the functions and let individual pipelines put together their stages by piecing functions together. This can be done with something like this:
T-shirt estimation is the idea, that estimation of user stories or tasks should be done at a rather rough level (t-shirt sizes) rather than precise hour or even storypoints. The idea is to save time, frustration and avoiding a false sense of knowledge by not trying to be more precise than actually usefull. It often turns out to be rather more precise than expected and with a good knowledge-pr-time-spend ratio.
Story mapping is a tehchnique used for both scoping and release planning of new projects and enhancements to existing products. It is very much inspired by the work of Jeff Patton made popular through his 2008 blog post “The new backlog is a map”, but in an adjusted form and combined with journey mapping practices and techniques.
This post is a practical guide of how to conduct a story mapping workshop with lists of things to rememer and do.