Where Agile Breaks Down (and what to do about it)
What if you’ve got dozens of developers in an agile environment and you’re still struggling to get apps out the door? Is your workload really that much bigger than your resources? Or could the problem be that some of your teams are really just doing “Agile Lite”? It’s something we see all the time. Yet it can be very easy to fix. Here’s how one company tackled it….
Five Things You Should Never Say in an Agile Environment
Deciding to deploy Agile is easy. Doing it isn’t. Even if you know the basics of Agile development – your teams can quickly get frustrated with subpar results, because they aren’t deploying Agile correctly. If you want to see great Agile results, make sure you never hear yourself say one of these five things....
How to Build Mobile Apps with Reusable Components
So you want your enterprise to reuse the same component in different apps? Smart move. Let’s say your component is a barcode scanner or signature capture. What happens? Your development organization creates it for one app. Then, they copy the code and change it slightly for the next app. Right? Wrong! The minute you change one line of code, your component is no longer reusable. Here’s what your team should do instead….
How Agile are you really? Take this Quiz to find out.
Let’s be honest. What a lot of teams call “Agile development” is really just Waterfall without all the documentation. How about your organization? Are you truly Agile? Or are you just treading the no man’s land between Agile and Waterfall without seeing the full benefits of either? Take this quick
Five Helpful Tips for doing Agile QA
QA is no longer measured just by the number of defects found. The real goal of agile QA is to improve the software – not just give it a pass or fail at the end. You want to provide valuable information for the next iteration. That means quality is the whole team’s responsibility.
If it’s not Tested, It’s not Agile
Be honest with yourself – is your agile implementation really just waterfall in disguise? If you aren’t testing as you go, the answer is probably yes. Too many companies often approach agile as “waterfall without documentation”, leaving QA until the very end while reaping the short-term wins of staying on schedule. That would be great, except for one thing…
How to Reduce QA Testing from Weeks to Hours (4 Simple Steps)
You know how important it is to test at the end of each sprint. But testing manually at every step is guaranteed to put you behind. If you automate your testing, you can boil three weeks of labor down to as little as eight hours of automation and save your human resources for the most sophisticated tasks. Here’s how.
Why the Finish Line for your Sprints isn’t Where You Think it is
One of the biggest surprises in an agile environment is that you can have completed code at the end of your two-week sprint and still not cross the finish line. What’s the problem? Testing. You know you’re supposed to test at the end of each sprint, but with goals to meet, it’s tempting to rush past QA. The problem is you’re not reaching your goals if you’re not testing, and bypassing QA comes with extra costs. Here’s what you need to know.
Protect Your Enterprise from “Disappearing App Syndrome”
When the volume of mobile activity exploded, enterprises that didn’t have the expertise or bandwidth to develop all their own apps had to scramble for help wherever they could find it. Often this meant turning to any boutique provider or independent developer who could get the work done quickly. In the end, the enterprises got their apps, but they also got an unintended consequence that needs to stop now.