- Case Studies
To help teams mitigate risks and other concerns — and make them explicit and visible — I like to do a RAID brainstorm, either at a kickoff/inception and/or at points after a project has started.
Forecasting: Blog Post 3 of 3
Here is blog post number three of John Yorke’s series on forecasting. In part one of John’s analysis, he looked at why forecasting is needed and some of the differences between forecasting and estimating. In part two, John laid out some of the different reasons why forecasting is needed.
Forecasting: Asking Why and Discovering What’s Behind the When
By John Yorke, WWT Asynchrony Labs Agile Coach
Forecasting: Blog Post 2 of 3
This is part two of John Yorke’s blog series about forecasting. In part one, John looked at why forecasting is needed and some of the differences between forecasting and estimating. In this post, he discusses the different reasons forecasting is needed.
When I started as a dev on an Asynchrony delivery team, I was excited to discover that I would have the opportunity to work directly with talented UX experts. This would have been a luxury at other places where I had developed software, as we never had easy access to these masters of design, layout, font, colors, and human-computer interaction. In reality, many of our UI decisions ended up being based on discussions that included comments like, “I think I may remember reading about how this form should behave in that Don’t Make me Think book”. As a result being able to consult with the UX professionals here, the single page apps and mobile apps (and Apple TV apps!) we build offer a far greater user experience, allowing our users to effectively and efficiently accomplish tasks and get the information they need. However, I am now working as a dev on Han Shot First — a team that creates HTTP services as a backend for mobile and web apps. Although we do not have a traditional front-end, does our API-oriented team need to be concerned with UX? As it turns out, the answer is “yes”!