Recently, we’ve introduced Commitment Based Estimation to a couple of our software teams. Typically, this helps a team provide highly-accurate estimates. These teams go on to deliver successfully by meeting these estimates.
Many business users feel as though requirements definition is a waste of their time. Learn how to get the most out of them and become a better partner.
Learn how some prototyping can decrease your chance for project success.
Learn how to overcome the biggest obstacle any team has to getting consistent estimates — our attitude towards estimates.
How recognizing “Spellcheckers” can decrease ambiguity around details and increase project success.
Learn how Iteration Zero can help lay the foundation for a successful project regardless of the development methodology.
Special guest of Geneca, Forrester Analyst, Mary Gerush, shared some valuable insight on why requirements definition is the key to avoiding project failure. Says Mary, requirements “must be a collaborative, business driven approach” in order to get the business what it needs. Here are some key points from that presentation and a link to replay the webinar in its entirety.