Month: October 2014
(see also: Agile Moment: Equating Story Points to Time, Scrum Effort Estimation, Practical Guide Story Points Estimation, How Story Points relate to hours, Story Points vs. Task Hours, Planning Poker)
Estimating story points for user stories that implement features on the Scrum teams product roadmap / product backlog is a critical planning exercise. All Scrum teams should utilize planning methods to estimate engineering efforts for future work. There are many possible methods available to estimate effort. However, for teams that are using Agile frameworks like Scrum, a proven, highly effective method of choice is Planning Poker. The overall goal of planning poker is to establish a clear consensus on an estimate for a given scope of work or user story.
Normalization of a relative estimating technique is absolutely critical for a team to reach a high-performance state. This also directly impacts an organization’s ability to perform capacity planning and management in scaled Agile applications.
What a really, really stupid and unconstitutional idea. That is, for the Federal Government to dictate to private companies that they publish private information.
First there was #antennaegate, then the infusible stories on the new Apple iPhone 6 bending (see 5 million articles/posts/videos of whining on #bendgate) under 80 lbs or more of highly unusual physical forces. Now the media and fashion challenged (read: nimrods who stuff their expensive tech in tight fitting jeans, then bend over) people are stuck in “we don’t have a story” mode again (or I’m bored and have no journalism skills?) with a dig on Samsung over #gapgate. Read the rest of this entry »
Jim Whitehurst discussed the interactions or lack thereof between infrastructure and operational folks and the guys who are locked in the closet – developers – in an interview with Fredric Paul (Network World). They discussed the fact that software is becoming ever more omnipresent in technology. It is the first level of interaction for users. People do tend to tune out the sleek new hardware and focus on the software experience. And it better be a good one! Not many end users care about the backend. So, Whitehurst asks the important question… Read the rest of this entry »