Test-First Programming for Improved Software, or Revisiting Red-Green-Refactor
We practice test-first programming because it enables us to improve the design of the system every day. We start by defining clear expectations for the system, in the form of executable specifications. Through constant refinement, we pursue simple and reliable designs.
At Def Method, we use Agile Methodologies or Scrum when working with client teams. While Agile can feel a bit “buzz-wordy”, we believe in the core tenants of the philosophy - rapid iteration cycles and clear communication across the team makes for great products.
Project Length Calculator
Are you curious about roughly how long it may take to create the application you are looking to build? Play around with our project length calculator to get rough, high-level estimates. Reach out to us and we'll run through a more detailed estimation process for you.
Code Reuse in the Delivery of Value
We make software in order to deliver the value to be gained from its use. The time and cost constraints inherent to the delivery of business value make it important to practice sound decision making in the most time-consuming and expensive software engineering activities: writing and maintaining code.
How to Communicate Effectively with Your Engineering Team
At Def Method, we work with many non-technical business leaders as well as technical team members and understand that it can be difficult when the two groups don’t “speak the same language”. If you’ve found it challenging communicating with your engineers, you are not alone, and we’d like to help. Here are some tips on how to improve communication with your engineering team and streamline your development process.
What is Continuous Integration?
If you ask ten people what they think about Continuous Integration, you will get eleven different opinions. Between various tools, rules and values, every developer/organization has a different opinion about what Continuous Integration (CI) is, what it means to the company, and how to implement it.
How to Run a Successful Project Retrospective
A retrospective provides a way to reflect on the software development work done in the past sprint cycle or cycles. It helps the team learn from past mistakes and improve their development process in the next iteration of work. We encourage regular retrospectives at the end of each development cycle.
Why Insist on Standups and IPMs
If you’ve been around techies, the terms “standup” and “planning meeting” might be familiar to you. For the uninitiated, standups and planning meetings are a standard activity for every agile team. These meetings facilitate the core beauty of agile development, namely customer collaboration and the ability to respond to change.
Discovering Your Product Before Jumping Into Development
At Def Method, we work with a lot of companies looking to build out their MVP. To kick off this process, we encourage founders to go through what we call a Discovery Process. During this deep-dive workshop that lasts two to five days, the Def Method team collaborates with you to clearly outline what you’re building and how you’re building it. Through a series of intensive exercises and product design/prioritization, we help to align the team on product goals and scope.