Mark Randolph

  

Sr. IT Specialist, Echota Technologies

Location: Kansas City, MO USA


Certifications

Certified ScrumMaster

Biography

My career is dedicated to finding and applying best practice software development methods.  Because of extraordinarily diverse skills in all aspects of Software Engineering, I am especially effective as Director of Software Development, Software Team Lead, or Senior Software Engineer charged with on-time delivery of defect free software.

Recent experience includes organizing and running Agile/Extreme programming teams at USDA and SAIC; Master level knowledge of Object Oriented Analysis & Design with UML (OOA&D); Sun Certified Java Programmer 6.0 (SCJP 6.0); Master level knowledge of C++; Software Configuration Management with Subversion; Rational Unified Process (RUP); BSc. Civil Engineering, University of Illinois; MSc. Civil Engineering, University of Illinois; Registered Professional Engineer (PE); Former computer programming instructor; Exceptional Writing Ability; Exceptional Speaking Ability. 

Articles I've written

Scrum Smells: Talking Chickens
Importance Important Symptoms These are symptoms that a Scrum team is not being protected from outside influences: External stakeholders talk in the daily Scrums Features are selected or priorities switched outside of sprint planning meetin...

Scrum Smells: Loss of Rhythm
Importance Very high Symptoms Lack of rhythm has a variety of odors, all related to inconsistency: Daily Scrum ritual is inconsistent or is drifting (subtly changing) Daily Scrums are skipped or meeting times vary Sprint durations are inc...

Agile Smells: Lack of Progress
Progress smells often point to failings in one of three areas: backlog management, feature definition, and feature completion. This article analyzes what lack of progress means and describes remedies for weaknesses in backlog management. Parts two and three of this smell analysis will address feature definition and completion, respectively.

Missing Pigs
Our series on Scrum smells continues with a discussion of what to do when developers fail to attend daily Scrums.