Member since 3 years
Specialises In (based on submitted proposals)
I help organizations build valuable software. Period.
Overcoming Dys-functional Programming. Leverage & transcend years of OO know-how with FP.Shawn ButtonAgile CoachLeanintuitDeclan WhelanAgile CoachLeanintuit
schedule 3 months agoSold Out!
Interest in Functional Programming has exploded in recent years. If you are an experienced OO developer, your design techniques and coding practices can easily get in the way of FP success. It certainly did for us! Fortunately, there are ways to leverage what you already know, to allow you to take advantage of the powerful tools FP can provide.
Join Declan and Shawn in this interactive session. Experience how FP can improve your existing code and simplify your design. Explore the joys and challenges of improving your Object Oriented skills with Functional Programming.
Technical Debt is a Systemic Problem - Not a Personal FailingDeclan WhelanAgile CoachLeanintuit
schedule 2 years agoSold Out!
You often hear technical debt described as a personal failing. Why didn't you code with greater rigor? By creating technical debt, how could you have made life harder on people working in the code? More often than not, technical debt is the result of bigger, systemic problems.
Chances are, you're not a bad person. You didn't want this to happen. It's the system, not you, that's chiefly responsible.
In this talk, we will present some of the conclusions from the Agile Alliance's technical debt working group, which has looked into the systemic causes and consequences of technical debt. While marginal amounts of technical debt will always accrue, that does not explain why substantial technical debt is a widespread phenomenon. The organization in which software development teams work is the much bigger culprit. Many systemic causes, such as deadline pressures, under-investment in skills, and even the unwillingness to measure technical debt, conspire to create a growing burden on software professionals, who would otherwise choose not to create this problem if given the opportunity.
Just as technical debt has systemic causes, the real cost of technical debt lies at the system level. The increasing drag on software innovation has effects not just on individual and team productivity, but on the software value stream, the portfolio, and the organization as a whole. Sometimes, the cost is obvious, such as the valuation of a start-up company's code; other times, the consequences are far more subtle and insidious.
During this session, we will use the language and methods of systems theory to better come to grips with the causes and consequences of technical debt. Don't worry if systems thinking is unfamiliar — we will cover the basics during the talk. We will also do an exercise in which you will create a simple systems model of your own challenges with technical debt, and discuss how this model should help you shape a plan of action for dealing with technical debt.
Ultimately, the goal of this session is to give you the tools to better deal with technical debt. Rather than blaming individual developers, you will be able to show the systemic sources of technical debt, and assess the relative value of addressing each of them. Rather than depending on technical measures to convey the costs of technical debt, we will help you to put the costs of technical debt in stark business terms.
Moving from Technical Debt to Technical HealthDeclan WhelanAgile CoachLeanintuit
schedule 3 years agoSold Out!
Everyone agrees that technical debt is a burden on software innovation that we would rather avoid, and certainly clean up whenever possible. However, in most organizations, people don't prevent technical debt nearly as much as they should, and they don't ever get the time to clean it up. Why, then, if there are clear incentives to deal with technical debt, is it a rampant problem?
In this session, we will focus on how to deal with technical debt on several levels, including the individual developer, the team, the software value stream, and the larger organization. While technical debt may manifest itself in a developer's IDE, the problem starts long before the developer decides to copy and paste some code, or creates an overly-complex and under-documented class. The pressures on teams and individuals to take on more debt than they should come from many sources. Therefore, the solutions to the technical debt problem must extend beyond the team.
No more submissions exist.
No more submissions exist.