Quality of project proposals, in terms of the accuracy in efforts as a response to a bid, plays a major role in winning the business. This article highlights important factors to be considered during proposal writing.
As a test professional in waterfall, I was used to getting the code much later and buggier than I expected and being under tremendous pressure to finish my testing before the go-live date hit. Then one day, I found out that there was a better way. Testers could be involved much earlier in the lifecycle, they could participate in requirements and design decisions as they happened, and the code could actually be unit tested before I received it! Heaven? Nope, agile.
Iteration planning meetings for any agile team can be quite chaotic. People swarm in the meeting area collaborating on features, solutions, and schedules. To the untrained eye, the scene could cause worry lest the team falls into a destructive and disorientating type of chaos. But Michele Sliger says that there's no need to worry--the chaos that surrounds the team actually rejuvenates the collective mind.
In this interview for the Iterations newsletter, Heather Shanholtzer talks with Niel Nickolaisen about the Process Purpose Model, a tool to help identify which features you really need and which you can skip.
If they don't already, all companies should focus on delivering business value. Agile provides a means to maintain this focus.
Bob talks with Sanjiv Augustine about his work with Agile Project/Portfolio Management and the Middle Managers that execute projects within organizations.
The author walks you through the details of actually implementing a continuous quality automation infrastructure. He builds up an example that addresses both the key principles and feedback cycles.
Everyone responds to change differently, whether managers know this or not. A good leader knows this, and doesn't hurt the morale of a team by expecting them to act a way that their incapable of, or that feels unnatural to them. Naomi Karten brings this all to light in this article.
I begin this story by declaring up front that I am not an "Agilist" or process evangelist. I am the senior software development executive in a company responsible for delivering products to the marketplace. Like my peers across industries, I am fundamentally held accountable by my company for consistently delivering business results. Process and methodologies are important in delivering this value, but in the eyes of the company they are secondary to meeting the needs of the business.
Becoming more Agile involves significant changes in the way that we work on a day-to-day basis. One of the central reasons that many technology professionals embrace Agility is its best practices which enhance the Quality of an application effort. Agile practices cut straight to the reasons that many projects fail. Of course, many organizations have also seen that adopting Agile practices does not automatically guarantee them improved Quality either. What practices should you focus on to ensure that your development efforts benefit from Agile's wisdom in terms of improved quality and productivity?
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!|