Articles

Better End Products Why Prototyping First Leads to Better End Products

Even with pages of documentation, there still can be miscommunication and misguided assumptions about a product. A prototype serves as the vision for the product and helps everyone, from a salesperson to an engineer, understand what they are trying to achieve. This article looks at some of the benefits of prototyping early in the development process.

Jessica Hall's picture Jessica Hall
Simple and Fast in Business Why Does the Business Think Everything Should Be Simple, Fast, and Cheap?

Whether they're on the business side or the IT side, professionals in the software industry tend to agree that more communication about project expectations is needed. So why is it that when the two sides collaborate, bad things seem to happen? Ryan McClish and Kenton Bohn analyze the human dynamics and show how to build a solution that accomplishes the defined goals.

Kenton Bohn's picture Kenton Bohn Ryan McClish
Spiral of an Organization Avoiding the Organizational Death Spiral

The death spiral supersedes the death march in that the death march is a singular event, whereas the death spiral is systemic. It is the result of organizational dysfunction where teams march toward deadline after deadline without reflecting on or questioning if there is a better way to deliver software. There is! Take these positive steps.

Thomas Wessel's picture Thomas Wessel
Performance Testing on a Budget Practical Performance Testing on Any Budget

Testing application performance prior to release is an essential part of managing risk in any software project. But the budget must be considered when talking performance testing; you want to know what it is going to cost to build and maintain a system that supports the project goals. However, there are ways to test the performance of your project while keeping the effort to a manageable set of tasks that get the job done without breaking the bank.

Stephen Gyves's picture Stephen Gyves
Software Product Discovery How a Software Tester Helps During Product Discovery

A software tester can begin testing early—very early—before the software has even been built. Karen Johnson explains that one of the best times to start testing a product is in the product-discovery phase.

Karen N. Johnson's picture Karen N. Johnson
Agile World Typewriter Writing in an Agile World

Sarah Johnson explains the role of writing in an agile world and how to educate your team members. Remember, agile takes into account that each situation is unique, and you need to determine what makes the most sense for your particular Scrum team.

Sarah Johnson's picture Sarah Johnson
Communicating Effectively in Agile Development Projects Communicating Effectively in Agile Development Projects

In today’s fast-paced workplace, software developers and project managers are confronted with a painful paradox. They are faced with continual pressure to accelerate the development process, but this “need for speed” can result in communication failures—and the accompanying project and quality problems.

Payson Hall's picture Payson Hall
The Self-Abuse of Sprint Commitment The Self-Abuse of Sprint Commitment

Adam Yuret explains what can go wrong when teams blindly commit themselves to sprints; collaboration and quality suffer when we pressure people to work themselves to death by forcing them to promise things they cannot yet understand. Investing in systems-thinking approaches to improve the lives of our workers will pay dividends in improved quality, engagement, and creativity.

Adam Yuret's picture Adam Yuret
 Assumptions to Model Value (or Not) Using Goals, Objectives, and Assumptions to Model Value (or Not)

Kent McDonald writes that identifying objectives and the assumptions underlying them provides you a way to measure whether the result of your project will actually get you closer to what you are trying to accomplish, as well as the impact your various assumptions have on reaching that objective. 

Kent J. McDonald's picture Kent J. McDonald
Using Agile for Requirements Management Using Agile for Requirements Management

Charuta Phansalkar writes on the necessity of capturing and understanding requirements using agile practices. Agile, when implemented effectively, will ensure that the customer's voice is clearly understood throughout the project, which results in maximum customer satisfaction.

Charuta Phansalkar's picture Charuta Phansalkar

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.