Blog

  • Resilience – A Strong Metric

    Resilience – A Strong Metric

    I was recently attending a conference (virtually, of course) that focuses on leadership and the related trends. Every year there is an idea or two that is the current hot topic. This focus has included familiar things like EQ and grit in the past years. One somewhat new theme this year was resilience. It is a trait we have all heard of, but it may be the next big thing to measure in getting the “best” employees. It may also be a metric you can use to determine how to improve yourself professionally and in your personal life.

    Resilience Assumes Challenges

    There is an old phrase, “hope for the best and plan for the worst.” It is safe to say that most of us accept that life will be full of challenges. It is hard to live very long without that being proven out. Therefore, our ability to react to and overcome obstacles is a critical factor in our success. You hear this concept in sports all the time. Every championship team had moments where they overcame a challenge and advanced on the path to becoming a champion. Every business’s success is the same. There are “overnight” successes that come faster than expected. However, most companies have a long and bumpy history that continues to the current moment.

    A Measure of Succes

    When you assume that every journey will include obstacles you must also accept that every journey has an opportunity for being derailed. There are substantial obstacles to face like the global shutdown due to COVID. However, there are more often smaller obstacles like a change in requirements or delays or miscommunication. We are required to overcome all of these to reach success. That logically flows to the idea of building a team that possesses resilience. This trait can come from individuals or it can be how the team members support each other. Sometimes there is not only safety in numbers, but also resilience.

    Positive Attitude

    The points made thus far are realistic, not pessimistic. Stuff happens. We can rail against it or bemoan our situation. Nevertheless, it is where we find ourselves. When we face these situations we can move forward or dwell on our misfortune. It seems obvious that moving forward is the best approach. However, we sometimes get stuck in these challenging moments. Resilient people take these sort of setbacks in stride. That is not only a valuable trait, it is also one that is relatively easy to see. Of course, levels of resilience can be difficult to measure, but it is not hard to see if someone possesses some level of it.

    Tactics and Approaches

    At the risk of being obvious, I think it is worthwhile to look at some of the things we see in resilient individuals or teams. There are actions that come from this trait and show that tendency to push forward. Here are some things to look for that can easily be worked into an interview (or self-reflection).

    • Acceptance – Moving requires action. Thus, the time spent on bemoaning a situation increases the time spent on it.
    • Blame – Looking for blame or a way to shift responsibility to others does not contribute to overcoming the obstacle.
    • Progress – Resilient people and teams move through options and avoid getting stuck on a single option as well as analysis paralysis.
    • Optimistic – It is hard to tackle a problem that you think is a lost cause. Resilience almost requires some element of a positive attitude or at least hope.
    • Analysis – One can spend too long analyzing a situation. However, resilient people have the ability to dig into a challenge in an unemotional way in order to see where things went wrong or look for ways out of it.
    • Roll With It – Much like acceptance, resilience often includes an ability to “shrug off” setbacks. Thus, challenges are assumed to exist and do not slow down teams or individuals with this trait. This factor points back to that “plan for the worst” concept.
    • Absolutes and Clarity – In my personal experience, I find that resilient people are less likely to talk in absolutes when talking about an approach. They leave open the idea that changes to their plans may (or will) be required.

    Nothing New Under The Sun

    All of us have been exposed to the resilient trait in people and teams. However, it can often be lost in the shuffle of other skills and attributes we look for in a team or hire. Therefore, it is worth our time to consider how it can factor into our approach and processes. There is no question that finding the right hire and building a team are complex and complicated feats. Likewise, we must avoid letting critical factors fall through the cracks.

  • The Agile Manifesto – A Practical Look

    The Agile Manifesto – A Practical Look

    The Agile manifesto started an entire industry. It has even been the focus of numerous “religious” debates and arguments. However, it has a lot of wisdom within it that is often overlooked. The main ideas are as relevant today as they were when it was first crafted. Therefore, it is worth our time to review some of these wise nuggets and consider applying them throughout our software development efforts.

    The Manifesto Is Not The Agile Methodology

    We need to start by clarifying that the Agile Manifesto is not the same as the Agile Methodology for building software. The manifesto was used to create the methodology. However, they are not one and the same. Think of the methodology as an attempt to turn the manifesto ideas into reality. It is easy to see where many agile or extreme programming techniques got their start in the manifesto. Nevertheless, your opinion (and experience) of one may be noticeably different from the other.

    The manifesto came out of a desire to create better software. The first point drives that concept home. The highest priority is to satisfy the customer. This statement should be the “why” of any application and cannot be turned into a process. The Agile methodology provides a lot of ways to assist in this goal but does not guarantee it. Looking at it that way, we can easily see where a team could use Agile methodology precisely as described and still fail to deliver a successful project.

    Work As A Realist, Focused on Delivery

    There are twelve points the Agile Manifesto lays out.  These emphasize producing a solution the customer wants while acknowledging the realities of software development.  The most important of these practicalities, to me, is delivering results along the way to the final solution.  This process recognizes that customers often change their minds, communication problems exist, and showing is better than explaining.

    We all know there is often a disconnect between business representatives and technical resources.  The language does not always translate and skilled liaisons are in short supply.  Thus, we can lower the bar by deciding to be flexible from the start.  This approach is not a way to ignore requirements gathering, design, or other due diligence.  Instead, it assumes we will need to revisit those steps.

    The Manifesto Points

    Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

    Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.

    Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

    Business people and developers must work together daily throughout the project.

    Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

    The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

    Working software is the primary measure of progress.

    Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

    Continuous attention to technical excellence and good design enhances agility.

    Simplicity–the art of maximizing the amount of work not done–is essential.

    The best architectures, requirements, and designs emerge from self-organizing teams.

    At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

    The Agile Manifesto

    Work Together For A Common Goal

     There are numerous rules of software development built into this manifesto that are needed for a successful product.  We already stated a focus on making the customer happy.  This statement is not arguable.  A product that does not please the customer is a failure by definition.  Another important concept that is woven throughout the manifesto is the Pareto Principle.  This rule says that 80% of our effort is spent in the last 20% of the product.  That means we can get “mostly there” relatively quickly. This focus on getting most of the way to the solution is highly valuable.  

    Let’s think about that a bit.  When you are almost done, you likely have a lot of the core functionality covered.  The “happy path” is complete and functional.  That is an essential factor in getting feedback.  You have a use for the product the customer can see and experience.  They have something concrete to assess and a solid basis for requesting changes.  

    Gaps In Knowledge

    It is not very different from taking a vehicle for a test drive.  You can get a feel for it and might even see some weaknesses.  This last factor is critical to the success of a product.  Customers should not be required to know edge cases and outliers in building a solution.  That is up to the developers.  However, these are issues that often fall into the “you do not know what you do not know” category.  When you provide a demo or partially complete solution, you give the customer a straw man to work with.  That is far more concrete and relatable than describing functionality or showing them a flow chart.

    Keep It Simple Somehow

    The focus on delivering regularly and the underlying Pareto principle ideas lead us to opportunities for the KISS approach.  It is amazing how often customers will scope out requirements to get working software in their hands sooner.  This carrot is dangled in front of them during regular demos and releases.  Yes, there are gaps.  However, a good relationship with a customer can lead to a shorter path to something they want and consider “done.”  Who would argue against that?

    Remain Flexible

    The last central theme I want to point out is the focus on change. When we create software, it is crucial to think about flexibility. We are not building a system to solve a specific problem and situation. Instead, we are trying to provide a solution that is useful in a broad range of configurations. The world is also constantly changing. Therefore, even though we can be assured of a need for new versions of our software, we need to be smart about it. A sound system is built with growth and change assumed. That means we need to prepare for it from the architecture through to each step of implementation.

    The Agile Manifesto has been around for many years. Nevertheless, it still is needed to remind software developers and teams of what is important. When we embrace these core concepts it reduces risk and improves our chances for success.

  • The Danger Of Almost Complete Software

    The Danger Of Almost Complete Software

    It is hard to keep up with the number of times I have worked into a phase of “almost complete software.” We often see this as a marker or milestone that tells us a little push is all that is left. However, that is rarely the case. It seems like the end of the implementation phase is a trigger for this lofty status. We all fall for it. Our product implementation is approaching a final milestone and extend that to being almost done. We overlook so many details that are yet to be done. In listing out some of these details, I am hoping that we can all be a little more realistic in our expectations and setting the same.

    Testing Almost Complete Software

    Testing cycles can be very short and almost ignored. However, that often ends in low-quality software and unhappy customers. A proper testing cycle can be time-consuming and will often churn on a couple of bugs or features. It is rare for e a project to sail through testing without time spent clarifying issues, how to reproduce bugs and requirement reviews. This phase alone can make the almost complete software claim seem laughable.

    Deployment Challenges

    Things are getting better with modern CI/CD processes and tools like Docker. These tools and processes help us start working on deployment issues sooner in the SDLC process. However, there is no replacement for the final deployment. It is amazing how often simple things like a point release difference in software, a seemingly negligible configuration value, or changing an address or network can bring down software. Even worse, the errors that appear in production and can not be seen in development often take a while to be identified. That also means these can take a lot of time to track down and correct.

    Understandably, one would feel close to the end at this point. The gotcha is that putting something on a production server is when the rubber truly hits the road. User Experience becomes a much more critical factor, and you often see load impact for the first time when you hit production. While many of these issues are addressed in future releases, I have also seen products languish amid deployment issues.

    Edge Cases

    A good set of requirements that are used to measure progress can help with this issue. Nevertheless, it is not uncommon to run into edge cases and unusual situations that only become visible when you get near the end of a project. These can be attributed to going after “low-hanging fruit” early on in testing and implementation. On the other hand, when we consider the 80-20 rule, this makes all kinds of sense. The two ideas are likely closely related. That last fifth of your journey in building software is going to be beyond the bugs that are easy to identify and fix. You are now in the area where significant challenges like “randomly” appearing bugs and race conditions need to be tackled. These alone can convert almost complete software to early steps in a death march.

    I apologize, but I have been on a kick thinking about anti-patterns. They are fascinating to me and an essential part of planning for success. If you want to learn more, then you can find more about anti-patterns all over the web. There are some patterns out there as well, but if you at least avoid some of these project planning, estimation, and execution anti-patterns, your odds of success will increase significantly.