Once you start unit testing, you will find significant benefits to your design, throughput, quality, and peace of mind. However, it is not easy to start in an organization that’s not used to it. Here are a number of practical tips:
Certified SAFe® Release Train Engineer. – Scaled Agile piplanning App Distributed PI Planning – Scaled Agile Framework Agile Processes Demo Board, Online Whiteboard for Visual
TL;DR
Use git, use eslint, and write unit tests.
Want to know the reasoning behind each tool? Keep reading!
Introduction
Whether you are starting out as a developer or already have some experience, improving your coding skills is an ongoing endeavor. But what does it mean to be a better coder?
While there are many ways to solve a problem with code, some of them are better than others. As Robert Martin wrote:
Even bad code can function. But if code isn’t clean, it can bring a development organization to its knees.
SAFe™ (The Scaled Agile Framework) uses Story Points throughout the various levels as its estimation currency. This is covered in the “Story” article on the SAFe site. This is a pretty standard practice in organizations scaling agile these days. If you dive a bit deeper into how this is done in SAFe you will see that actually the story points used in SAFe are quite similar to “Ideal Developer Day” as this helps the teams align to a common baseline and support a rational economic ROI discussion at the level of Features/Capabilities that require effort from more than one team or haven’t even been mapped to a specific team yet.
The Sprint Increment Got Us Here
If you’re a veteran of the software industry, you probably remember those days when we released to production/GA every couple of months. Heck, many of the companies I meet these days still work that way.
If you’re also an experienced Scrum practitioner, you probably associate the time you started to use Scrum with the time you started to release more frequently. The Sprint Increment that had to be potentially releasable caused you a lot of pain as you were trying to improve your processes and capabilities, implement Continuous Integration, and finally gain the ability to actually have a releasable Increment each Sprint. You were pretty proud.
Transformations naturally start with a change in the process and the tools, which inevitably create tension that is supposed to catalyze a deeper change in other elements of the culture. Many implementations struggle and even get stuck at that stage. This is the hard part since it is mostly about people’s behaviors and habits and it takes time. This is exactly where HR professionals come in! I’m not trying to say that only at this stage HR people start partnering and pushing the transformation, I am only emphasizing their importance at this stage. HR departments are key in leading Agile transformations to long, lasting and truly impactful ones.
Working with teams I sometimes feel that teamwork is similar to the weather: everybody talks about it but not much is done. When I talk about teamwork I mean doing the work together, as a team. Advising with each other is good, planning together is necessary, going to lunch as a group is fun and like the other activities, is probably a good way to get nearer to team work. However , as said above, I’m talking about doing the work together. And here are 3 steps that will help you get nearer to that worthy cause.
The Premise
A year ago Scrum.org, in collaboration with Daniel Vacanti and myself, published the Kanban Guide For Scrum Teams, a guide that is aimed at helping Scrum Teams take advantage of Kanban/Flow principles and practices. (I wrote an earlier blog post about understanding the guide)
SAFe™ has included Kanban at all levels since version 4.0. Some basic guidance about Kanban is included in most if not all SAFe curriculums. Can a SAFe practitioner learn anything from the Kanban Guide For Scrum Teams?
In this blog post, I’ll explore some of the flow metrics from the guide with an emphasis on those that aren’t covered in SAFe.
Keynote Speakers Organization, Architecture, Autonomy and Accountability Kevin Goldsmith, Chief Technology Officer @ onfido https://youtu.be/NdjURwdPvJM Project to Product How Value Stream Networks Will Transform IT
The console object is a very useful feature of browsers that have been around for many years. It provides access to the browser’s debugging console.
Most web developers know how to print messages to the console using console.log. But I’ve found that many don’t know about other features of the console, even though they can be very useful for every web developer
Request for additional information and prices