Some days you leave work feeling as if the day went by without an inkling of progress or productivity. Other days, you leave feeling as if you conquered the world, with an internal spark of satisfaction and anticipating resuming progress the next day. So, what is it that makes the difference?
Paul Poutanen has developed extensive mobile expertise working in management for wireless hardware and cellular location firms such as Wi-LAN and Cell-Loc before launching Mob4Hire in 2007. In this interview with Jonathan Kohl, Poutanen discusses the complex global testing process for mobile devices.
You may have a lot you need to say in a very short timeframe, but speak too quickly and those listening may not get the full message and they could end up missing out on crucial information. Make sure that the individuals you're speaking to can understand you clearly, or face the consequences.
Using an amusing medieval tale with a modern twist, Andrew Fuqua and Charles Suscheck tackle the dilemma of dealing with problematic overachievers in your agile team.
Testing an application's performance in the cloud begins with understanding the infrastructure of your public cloud environment. Learn which elements to watch for and how to optimize your cloud-based performance testing environment.
By understanding the context in which their existing practices were meant to work, teams new to agile can more easily decide which of those practices still make sense and which are simply security blankets.
Don't just shoot for yes or no answers from your customers, give them the opportunity to really share their feelings from their interaction with you. Areas where improvement is needed, or where praise should be given, will be far easier to spot, thus allowing you to really make valuable changes.
Testers are people who ask questions, think critically about the answers, and then ask more questions—repeatedly. Fiona Charles reminds testers that their success depends on maintaining a healthy skepticism.
This article explains methods to build a team that will embrace "required work" and deliver robust software in a predictable fashion. It proposes a measure that helps calculate the throughput of an agile team by comparing work committed to work actually done.
Uncertainty doesn't have to be a bad thing, but many say they'd rather know there were definitely problems coming, rather than be uncertain about whether there were or not. What do you prefer? Do you spend valuable time trying to prevent uncertainty?
Agile Test Automation
Successful Automation in an Agile Environment
Fundamentals of Agile Certification
A Pragmatic Approach to Adopting Agile
Be a Testing Rock Star
Agile Development Conference & Better Software Conference East
The Premier Collocated Conferences for Software Professionals
Recommended Web Seminars
Agile Connection is one of the growing communities of the TechWell network.
|Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery. Join the conversation now!|