As to the puzzle, I guess it's about modeling the problem in a manner similar to other business processes. Consider the game as a business process model of handling a software CR. Each chute is a potential setback (crap, found an error during QA, send it back to testing for analysis) and the ladders could be things that advance a process unusually quickly (we got the data from the customer on the error, turned out it isn't with our code but documentation on how to use the program, update the manual and bypass testing/SQA). Collect data over time, optimize away inefficiencies or deficiencies that induce extra work or rework.
[1] http://en.wikipedia.org/wiki/Operations_research
EDIT 2: Not sure if tired or autocorrect, but manor and manner are not the same thing.
I found the puzzle easy enough. It's just a matter of calculating how many moves are needed from square 11, then square 10, and so on. The chutes complicate matters a little, but not much.