Do you have a complex project with lots of parts to manage? Do you know which parts of your project are best developed incrementally and iteratively? Are you looking to cooperate with a designer, programmer, and teamwork expert who has 25+ years of professional coaching experience in America's silicon forest?
C. Carr's background includes semiconductors, computer manufacturing, and weapons-grade optics. Charles codes in C#, Lua, JavaScript, PHP and JSX. His skills in scrum have been honed through a half thousand sprint retrospectives and a dozen thousand standups.
Excellent Waterfall Is Better Than Mediocre Agile
Do you know when it's best to waterfall part of a project? Do you know when to sprint and when to cruise? Do you know where frameworks overlap and how to integrate their ideals? Do you know that marking increments via iteration need not lead to wasteful timeboxing and meetings for the sake of meetings? And do you know how to scale teamwork in the way that's best for your unique organization? Another important question: How much technical debt can leak beyond the frame of your current implementation (of a framework) ? How do you deal with that?
Scrum can be done without etching a sprint calendar full of mandates into stone. And really, every well-fit development framework should have the right measure of flexibility within it. And you should take full advantage of that flexibility while realizing every framework encounters problems it's incapable of solving. People matter. Situations and circumstances matter. Details are different from one part of a complex project to the next part. Real agility is being able to handle adversity.. Understanding how your unique teams function within the framework is key to overcoming adversity.
Manifesto consulting will tend to disconnect your business from reality and obscure the practical solutions you need for the socio-economic hierarchy in which we exist
Do random blog posts have you thinking about paying some kind of grandmaster-scrum-master who purchased a collection of initialisms to go after her/his name come into your space and, by pandering and preaching, sell you some high-purity "Agile" by the kilogram? Are you really going to buy into the utopian foolishness of the most popular and expensive honeypot in software publishing?
Perhaps you'd do a lot better with pragmatic solutions that come by way of innovation. Build upon what's been proven in frameworks. Why not take the best of the most performant while pushing any cookie-cutter boundaries as far as needed? Coach Carr can help you create a custom framework with the flexibility, predictable probabilities, and leadership roles that your business needs
Coach Carr can train his Academy's faculty from anywhere in the world, and since he doesn't mind traveling, you can negotiate his visit to your workplace in Europe or the USA. Please be aware that Coach Carr will come up with solutions to problems for you, but he will not sign a long-term contract with your company.
If your fab or IT project wants a walking, talking, buzzword-certificate collection, then leave here and go back to filtering submissions for your "Agile coach" ad on LinkedIn
However, if you're in need of an actual coach who acknowledges reality and was mentored by teamwork gurus in America's most competitive industry, then you may consider contacting him. Executive Coaching is not tutoring. You should figure minimum compensation for Charles to be thrice the hourly rate that's listed for Exclusive Time on the pricing page.
Think of this page as a preliminary cv and gig filter. And think of this paragraph as a lesson on the true origin of scrum- it actually developed in the USA a good number of years prior to any lean manufacturing in Japan.
Coach Carr was doing scrum several years before any mountain-top manifesto. Certainly, scrum's actual origins are much older than Charles, but he was intensely involved with the framework a whole decade before Jeff Sutherland and Ken Schwaber wrapped a commercial package around it. In fact, Charles started doing scrum the year before Hirotaka Takeuchi's article in Harvard Business Review.
If you are a CEO, recruiter, project manager or product/company /startup owner in dire need of the real deal with regards to executive coaching, teamwork, and proven-performant frameworks (for any industry) then feel free to ask Coach Carr how his experience can benefit your business.
He will consider scheduling time for interviews, but will not algorithmically slant documents (this website can serve as his CV) and he will not jump through any other HR hoops prior to actual conversations with human beings who are in need of an exceptionally talented coach. For even though Charles does indeed have a passion for helping organizations improve their teamwork, he does not need to work outside his own company.

Are you failing at scrum or do you struggle with implementing other Agile frameworks? How do you know how bad you really have it? One way you won't know is if devs secretly hate your meetings because they fear reprisal for not keeping such secrets. That's crazy costly
Here's one way to detect how badly you're doing (for example) - your dev team is always or almost always completing everything that gets listed on the sprint backlog.
If that particular goal line is usually getting crossed like it's a race, then your project management is a farce. Always or almost always "completing sprints" means that your company is utterly failing to do even bare-minimum scrum. And if you aren't aware of the truth such statistics tell, then you are in dire need of help
Another indicator of poor performance is this- a scrum master who typically expresses hope and enthusiasm for the delivery of every item on a sprint's backlog. That's something extremely detrimental to development
Seriously, any cheerleading or hopefulness for shipping increments is a really bad sign. If such an attitude is evident to you or the devs, it means that your HR onboarded a poser for the position of scrum master.
In either case, the results are the same- your company compounds catastrophic amounts of technical debt with every iteration, or it's hemorrhaging money right now from abject inefficiency and fake success, all caused by a severe lack of trust among key people involved in the project. All of the numerous possible causes of your problems must be identified and solved. How do you plan to go about that?
Fix it with Coach Carr