Skip to main content

George Dinwiddie

Profile picture for user gdinwiddie

Member for

19 years 8 months

George Dinwiddie helps organizations develop software more effectively. With thirty years of development experience from electronic hardware and embedded firmware to business information technology, he has broad technical experience. George helps organizations, managers, and teams solve their problems by providing coaching, mentoring, and training. Capable across the broad range from process improvements to engineering skills, George currently has special interests in team-building, skill-building, and effective collaboration techniques. Find George's blog at blog.gdinwiddie.com; his company, iDIA Computing, LLC, at www.idiacomputing.com; or email him at [email protected].

Company
iDIA Computing, LLC
Job Function
Consulting
Industry
Professional or Scientific or Technical Services
Interests
Process Improvement
Requirements
Software Testing
Country
United States

George Dinwiddie helps organizations develop software more effectively. With thirty years of development experience from electronic hardware and embedded firmware to business information technology, he has broad technical experience. George helps organizations, managers, and teams solve their problems by providing coaching, mentoring, and training. Capable across the broad range from process improvements to engineering skills, George currently has special interests in team-building, skill-building, and effective collaboration techniques. Find George's blog at blog.gdinwiddie.com; his company, iDIA Computing, LLC, at www.idiacomputing.com; or email him at [email protected].

All Articles by George Dinwiddie


All Stories by George Dinwiddie

Developing User Stories The Three Amigos Strategy of Developing User Stories

Developing software correctly is a detail-oriented business. George Dinwiddie writes on how using the Three Amigos strategy can help you develop great user stories. Remember, the goal is to have the work done just in time for planning and development. It should be complete enough to avoid stoppages to build more understanding, but not so far in advance that the details get stale.