If you are considering leaving the nest to self-fund your own endeavor, you may want to read about Mike Botsko's experience creating a cloud-based, bug-tracking app called Snowy Evening. What started out as a lot of fun quickly turned into a tough journey. Don't worry—it has a happy ending!
Taking lessons from the lean business model, Matt Heusser explains how a tester can present different values and properly set expectations with the team using the lean test canvas. His approach starts with defining who the customer is and ends with key qualitative measures that will be used to ensure success.
It can be a challenge for a product manager to know how to lead an agile software team. As product managers take on many different roles throughout a project lifecycle, there can be confusion, resulting in the product manager doing what nobody else wants to do. Steve Johnson offers a perspective of the agile product manager that every software developer should know.
A key characteristic of agile is that a team self-organizes to best fit the workload. This, according to Maria Matarelli, can be more difficult than the more traditional approach of a project manager simply telling the team what to do.
QA is often considered that lonely department of testers whose job is to find defects before the customer does. It's not always glamorous, but QA deserves to be recognized as a key cog in the testing machine. To achieve business goals, it is Susan Bradley's view that the QA process needs to be embraced throughout the entire software development lifecycle.
Many of us work for organizations that claim adherence to agility, yet in practice aren't even close. Agile is definitely here to stay, and if you haven't caught the wave, it is only a matter of time before you do. Brian Rabon presents insightful techniques that can help you become more agile now.
In this FAQ column, Arlen Bankston defines the roles of Scrum and kanban and describes how the two agile methodologies can be complementary, each ideal for different situations, or blended to achieve the desired outcome.
Probably one of the most frustrating roles a manager has to master is how to know the true status of work being performed. To a developer, completing 80 percent of the work may be good enough, but is it even close to being really done? Masha Nehme shows techniques you can use to verify task completion.
Johanna Rothman compares the experience a patient has with doctors to software development. Producing value implies that the customer believes the software you create provides an important benefit by taking into consideration the way a user works along with an exceptional user experience.
Eric Winquist has considerable experience not only leading his company but also consulting with development teams. His advice to “link people to the work” is one of many golden nuggets of information that will help your team deliver projects on time.