Our Mission

Scrum and agile have quickly become the status quo in many companies. Agile’s short delivery cycles can seem disruptive and chaotic, particularly for those of us who grew up on waterfall. Many companies ramped up by training a few scrum masters, leaving the developers to just "figure it out" on their own.

Adopting iterative management, planning, and delivery -- and not investing in iterative engineering -- is a recipe for pain.

What is your pain level?

Can you spot these common symptoms of agile-done-poorly?

• Iteration / sprint deliveries are more often missed than completed.
• Developers feel rushed and micromanaged.
• Developers feel pressured to deliver a poorly engineered product.
• Code quality suffers.
• Morale is low.
• Releases are missing key features.

Want to stop the pain? The road to recovery can begin by attending our training. As you grow your iterative engineering skills you'll move the pain needle toward the green end of the spectrum. Adding iterative development to your skills can do more than just relieve pain, you'll enjoy developing even more.

With Wingman Software, you’ll learn the engineering techniques needed to deliver working products with long useful lives. You’ll start on a path to a more enjoyable career doing the things you like most: solving problems, programming, and delivering useful products. You’ll also avoid the pain of delivering defects, debugging, and low morale.

Test-Driven Development (TDD) helps you prevent defects by putting mistakes in your face as you work. It's humbling and worth it. TDD will save you hours and days of aggravation. With TDD you work in a tight feedback loop, adding a failing test, then writing just enough code to pass the test. This cycle continues as you exercise and confirm each path through the code.

This probably sounds backwards or crazy. You will find it is an effective and natural way to work. As a bonus it's rewarding and fun too!

With TDD, development and test automation are part of every day. Each iteration you add new features and capabilities. The tests form a safety net that notifies you when your code no longer meets the specification designed into each test.

For more information about how TDD can save you from the defect chase, read The Physics of TDD.

Code change is inevitable. But how do you make changes to code that ensure the design stays clean? The test safety net, woven with TDD, allows you to safely refactor your code and keep your system from deteriorating. You will learn to identify code and design problems, envision better solutions, and keep your code working during the transformation.

Did you know it is easier to keep a system working, than to fix it after your break it!

Our courses will help you learn the critical skills needed confidently evolve existing code without introducing new problems. Read more about these critical skills here.

It is so natural for embedded developers to live with this pain. When hardware and software are concurrently developed, too often hardware is delivered late in the development cycle. A miracle is expected when the two come together. But there are no miracles in this line of work. If you rely on your target as the sole vehicle to test your code, get ready for pain and delays.

James first saw Test-Driven Development in 1999 and saw that TDD could help relieve the target-hardware bottleneck by first getting his code to behave in an off-target test environment. James lived with the pain for the first twenty years of his career. No more though, and you don,t have to either.

Our courses will help you learn to design for test (and consequently a long and useful life). You'll see how TDD and off-target test can help you break the target hardware bottleneck.

Read more about progress before hardware here.