zeman-j4

What this is about: Performing automated data backup saves teams a big hustle in case data gets lost. Doing so lowers team frustration, removes risk for a business and frees...

What this is about: It is important to oversee the crucial parts of systems and teams. Knowing a little can have disastrous results, knowing too much leads to decision paralysis....

What this is about: As every project fulfills its purpose, it is time to approach its conservation. It doesn't mean it will be shut down, rather only supported anymore and...

What this is about: Developers and operations should be both on the same team, yet there are often times clashes happening. Keeping both parties in sync is a necessity and...

What this is about: Mid-sprint activity focusing on going through the current backlog and "refining" items on the list by adding more detail and estimates. Knowledge received from the ongoing...

What this is about: Managing well the stream of demands is important to build a good product the right way at the right time. The ability of team leads and...

What this is about: Software always has to fulfill a purpose it is being built for. Having well defined acceptance criteria is essential for fulfilling such goal and gives developers...

What this is about: It is a common courtesy to let users know when one thing ends - product, version of API or library support. Provide deeper information on what...

What this is about: Using Business model canvas serves as having the added value business as a one pager. This helps employees understand the true nature of business and understand...

What this is about: Continuous delivery helps to get new tested features to users as fast as possible. Having this automated saves team members solid chunk of frustration and gives...