Relevant Retrospectives: Visualize how each Sprint Impacts your Codebase
These days it’s probably easier to track down the mythical Yeti than to find a software organization that hasn’t adopted some form of agile practices.
These days it’s probably easier to track down the mythical Yeti than to find a software organization that hasn’t adopted some form of agile practices.
When we started developing CodeScene, our overall goal was to show that there is more to code than code; we wanted to highlight–and make actionable–all the information that is invisible in the code itself.
CodeScene’s project management metrics let you measure where you spend your costs and how the development activity shifts over time.
Many organizations transition to short lived feature branches and employ practices like continuous integration/delivery.
CodeScene lets you uncover and prioritize code that’s hard to maintain or parts of the code that become team productivity bottlenecks.
The CodeScene analysis engine runs on git repositories.
CodeScene’s primary use is as a tactical tool to make technical and organizational decisions around your codebase.
Part 4: Scale-up - Analyzing Patterns in the Evolution of Linux
Part 3: Time - The Hidden Dimension of Software Design
Today I patched a monster.
Part 2: Novel Techniques to Prioritize Technical Debt
Part 1: Predict Maintenance Problems in Large Codebases
Watch CodeScene run the latest analysis results of your favorite open-source project.
Behavioral code analysis is a young discipline.
Security vulnerabilities correlate with low code health, development hotspots, and a high author churn in the organization.
Complex code slows down development productivity, increases the delivery risk, and leads to excess maintenance costs.
Four decades ago, Fred Brooks coined what we now know as Brooks’s Law: ”adding human resources to a late software project makes it later”.