Program planners in IT organizations have a dilemma: On one hand, their agile teams tell them that if requirements are defined up front, agile teams cannot operate; but on the other hand, the program’s budget and scope need to be defined so that resources can be allocated and contracts can be written for the work. How does one reconcile these conflicting demands?
Team members involved in hopeless projects become dejected, stressed, and overworked. Are there any silver linings to working on a doomed project? This article argues that there are. When you and your teammates are stretched to your limits, you can learn a lot about each other, your managers, and what it takes to make a successful product.
Developing software correctly is a detail-oriented business. George Dinwiddie writes on how using the Three Amigos strategy can help you develop great user stories. Remember, the goal is to have the work done just in time for planning and development. It should be complete enough to avoid stoppages to build more understanding, but not so far in advance that the details get stale.
Kristin Cowhey explains how z/OS development has evolved throughout the years and what that means for developers and tech personnel. With legacy developers leaving the workforce, there’s a dire need to replace the knowledge in order to maintain the mainframe systems and applications that are still in use today.
Alan Crouch addresses the question most commonly raised by those who are new to security testing: "How does security testing fit in my QA process?" Alan explains that security testing shouldn't be limited to the QA process, but instead should be applied throughout the entire software development lifecycle. Read this FAQ column for suggestions on how to improve your chances for success in catching security issues.
By emphasizing better communication and collaboration between software development and IT, this article explores ways to establish trust by focusing on customer value. For example, Manoj Khanna suggests continuous integration and validation as techniques that helps build that trust.
The software development field has been consumed with process management ranging from inflexible, predictive waterfall all the way to self-governing, adaptable agile approaches. You probably already utilize a specific process methodology on your projects, but have you considered adopting an evolutionary learning cycle process framework instead?
With mobile and small embedded devices extending the reach of modern computing, the predictions are that wearable computing is definitely the next biggest thing. If you want to know more about the wearable device revolution, Mukesh presents facts that will convince you this is the next hottest trend.
In this interview, principal consultant and Agile Artisans founder, Jared Richardson, explains how misunderstanding requirements can cause major issues within an organization. He covers why team members need to communicate, how big projects are often mishandled, and the value of agile.
Diane Zajac-Woodie sat down to discuss her upcoming presentation at Agile Development and Better Software Conference West 2014, why the business analyst role doesn't get the attention it deserves, how the BA role can make a difference on agile teams, and her alter ego as the Agile Squirrel.
In this interview, Mark Meretzky talks about his presentation at Agile Development and Better Software Conference West 2014, how he feels about Android versus iOS, his favorite programming language to teach at New York University, and what language he thinks programmers should learn first.
Jay and Danielle talk about their presentation at Agile Development and Better Software Conference West 2014, why teams should care about their mainframe systems going agile, the role of legacy tech in an agile world, and some ways that teams can modernize their development practices.
Many teams and organizations have found agile methods help them produce more. Where critical thinking is alive, a more important question arises: Are we producing the right thing? Even though agile tools and processes have helped produce more, they often fail to help us produce the right...
Many agile teams focus solely on velocity as their measure of progress. They draw burn-up charts to track it over time and make it the focus of much of their discussion during sprint planning and retrospectives. Is the strong focus on this metric truly in line with the principles of...
Jeff "Cheezy" Morgan, LeanDog and Ardita Karaj, EPAM
Since the dawn of computing, we've invented only two ways to get work done―the web or apps. We hunt for information on the web or we gather functionality from the app store. In each case, users must take the initiative to find the information they need...