With intermediate deliverables, you can help your product owner really see the value you've delivered and evaluate it usefully against their requirements.
Should documentation be done away with in Agile development? No! Good documentation can spark powerful conversation and collaboration.
A smooth mobile app release should include several kinds of testing, Alpha and Beta distribution, and phased rollouts.
Do your due diligence before picking out libraries, and you will save yourself a lot of headaches. Avoid things that are poorly maintained unless you want to end up maintaining the
How to think about the users you don't want so you can prevent, block, or report them from engaging in the experience you are building.
Agile isn’t about “doing practice X.” It’s about finding the set of practices that best meet the needs of a given team at a given time. That's not easy.
TypeScript is self-testing. When you use types as the bones of your system, it significantly changes your approach to testing, logic design, and more.
Our document-driven app needed a great authoring tool. We built one in record time using TypeScript, Visual Studio Code, and AWS Lambda.
As consultants, our high-level goals are obvious. But once we get down into the details of actually creating software, they get a lot more nebulous.
If multiple people have to be consulted for every decision, projects quickly grind to a halt. It’s time to stop inviting everyone to every meeting.
If an Agile team owns the process, they also own their team dynamics. Defining logistics upfront may be overhead, but it’s worth the investment.
Teams get stuck all the time, for a variety of reasons. The utility player is responsible for jumping in to get the rest of the team over the hurdle.