|
Pairing: The Secret Sauce of Agile Testing
Slideshow
Finding time to learn test techniques, mentor other testers, grow application knowledge, and cross-train your team members is a daunting task with a complicated recipe. What if you could do these things while testing and finding bugs? Enter Pair Testing. What’s that? Well, maybe you’ve...
|
Jess Lancaster
|
|
Identify Bottlenecks in Your Agile and DevOps Processes: An Interview with Tanya Kravtsov In this interview, Tanya Kravtsov, a director of QA at Audible, explains why identifying bottlenecks is so critical when you’re turning to agile and DevOps, as well as how automating manual processes can lead to better quality.
|
|
|
4 Balanced Metrics for Tracking Agile Teams Whatever your feelings on metrics, organizations will expect them for your team. You don't want to measure only one aspect to the detriment of other information, but you also don't want to measure too many things and scatter your team's focus. Here are four metrics that balance each other out and help gauge an agile team's productivity, work quality, predictability, and health.
|
|
|
Managing Risk in an Agile World Most software projects take great pains to identify and mitigate risks. Traditional risk analysis techniques can be subjective, time-consuming, and complicated. All it takes is a simple spreadsheet.
|
|
|
Back to Basics: Use the Heart of Agile to Frame Your Agile Adoption Somewhere along the way, agile implementations have gotten overblown and unwieldy. Managers and leaders look at all the models and frameworks and think agile adoption is too confusing or not worth the effort. To communicate what agile truly means, we have to simplify the message by getting to the heart of agile: collaborate, deliver, reflect, and improve.
|
|
|
Mapping Story points against hour Estimation Hi everyone,
I have just taken over responsibility as a a scrum master and although i have worked under a scrum team before for a year but i always had difficulty in estimating according to story points. So in my first prokject as a scrum master, I took a risk and though to map story points against hours and it went very well. Here is how i mapped:
Points - Hours
1 2-4
3 4-8
5 8-16
7 16-24
9 24+
When i gave them a range the team was very comfortable so what i did estimated it according to the table above and in the end they all had a rough time frame then when and how they are going to complete it. I need to know that if it is feasible in long run?
Need very valuable comments on this one :)
|
|
|
Reshaping Our View of Agile Transformation Transforming a software development team to agile may not go as planned. The real change requires a phased approach to earn agile acceptance. That mindset must extend beyond the team to the entire organization.
|
|
|
Agile Managers: Trust Your Team and Encourage Innovation In order to fully embrace agile and create an environment where individuals want to work together as a team, managers have to move from a role of dictation to one of direction and mentorship. Instead of making all the decisions, managers need to trust their team members and empower them to solve problems on their own, innovate, and fail—or succeed.
|
|
|
Let the Agile Manifesto Guide Your Software Testing Although its values are commonly associated with agile software development, the Agile Manifesto applies to all people and teams following the agile mindset, including testers. This article examines the four main values of the Agile Manifesto and reveals how they can bring agility to test efforts—improving quality for your team and your customers.
|
|
|
Leadership Lessons to Bolster Your Software Team: An Interview with Selena Delesie
Video
In this interview, visionary speaker Selena Delesie explains how successful teams embrace specific principles, including listening deeply, believing people truly matter, having an addiction to learning, serving others, flowing through change, moving through fear, and following joy.
|
|