Technical Debt a Perspective for Managers
Developers often talk about Technical Debt saying its slowing your projects down. What are they really saying? What measures can you take to reduce it before it cripples your projects?
InfoQ
InfoQ
Editor Specific Content View
Mark Levison
Mark is a Certified Scrum Trainer and Agile Coach with Agile Pain Relief Consulting. He has over twenty years experience in the IT industry, working as a Developer, Manager, Technical Lead, Architect and Consultant. He has ten years of experience with Agile and Scrum introducing these methods to a number teams from small companies to large organizations. He also publishes a blog: Notes from a Tool User. When not in front of a computer, Mark spends his time with his wife and two daughters.
All of Mark Levison's Content on InfoQ
Latest featured content by Mark Levison
The Science of Learning: Best Approaches for Your Brain
Why don't people understand your idea in a meeting? Why does the developer you're mentoring still not get it? Why do attendees in your course only learn 10% of the material? We are all teachers in some way, yet only professional educators receive training in this area. This article discusses lessons from neuroscience and how they can be applied to Agile Software Development and beyond.
Making TDD Stick: Problems and Solutions for Adopters
Mark Levison observed that, after solid classroom training, teams in larger companies still struggle to adopt TDD. To better understand the problem he surveyed team members. In this article he shares the problems he uncovered and his own comprehensive strategy, designed to help anyone introducing TDD into an organization.
News by Mark Levison
Agile/Scrum Retrospectives–Tips and Tricks
Retrospectives and feedback loops are at the heart of any successful Agile/Scrum implementation. They’re the tool we use to help teams improve. Yet in two day introduction to Agile classes they often get glossed over. Lacking time trainers (including this one) often race through the topic outlining only one simple type of retrospectives.
Working with Difficult People and Resistance in Scrum
How do you work with difficult and uncooperative people? People who are combative or unprofessional? People who seem actively opposed to the agenda?
Tips for Release Planning with Distributed Scrum
With teams in the US and India, how does one make release planning work? What if the team isn't even able to do their planning at the same time because of the time difference?
Selling Scrum to Your Manager?
Trying to Sell Scrum to Management? Failing and wondering why? This often happens in the days after someone returns from a CSM course ready to help change the world.
Sprint Burndowns - Are We Measuring the Wrong Things?
Does a the traditional Sprint Burndown chart help the team? A number of Scrum teams find that tracking task hours hides the true state of the sprint and prefer other tools.
Should the Best Scrum Team Be Rewarded?
Should one provide a reward to the single best team in a division each quarter? How is that team to be determined? What effects will that reward have?
