Carl Bruiners Agile / IT Development Consultant

Carl Bruiners

I specialise in all things Agile (XP, Kanban, Lean), in particular Scrum. I have a passion for taking on 'problem' projects / teams and turning them into a sucess as well as promoting automated test driven practices.

More

I am an enthusiastic, dedicated and accomplished Systems / application Architect, Project / Product Manager, Development Manager and Application Developer who thrives on delivering first class products.

My background is that of a developer who became a product / project manager and the head of application development. I am a certified SCRUM Master and have solid knowledge of PRINCE2.

I Work well on own initiative and can demonstrate high levels of motivation and organisation required to meet targets and deadlines. I have excellent interpersonal skills and communicate well at all levels.

Details

About Carl Bruiners
Contact Carl Bruiners
Carl Bruiners Twitter
Carl Bruiners LinkedIn
Carl Bruiners Scrum Alliance

Tags

.NET acceptance criteria Agile Agile Scrum wall ASP.NET Backlog Burn down C# Carl Bruiners Code Formatting CSS css play Defaqto Drivers Epic Tasks estimation Generator Girlguiding UK hats JS kanban Kinect Leadership Lean Luhn n-tier planning Product Backlog Product Manager Product Owner QA qaulity assurance Scrum Scrum Solutions Sprint Stories story test automation Testing The really simple Agile tool User story VB Vision Waterfall XP

Recent Posts

Categories

Blogroll

Archives

a really simple Agile tool

No current feedback
Powered By UserVoice.

Carl Bruiners Linkedin
Scrum Alliance - Carl Bruiners
Turbo Squid - Carl Bruiners

22Jan/120

Identifying an Epic using apple strudel

I recently had a work trip over to Stutensee in Germany, working with a team wanting to investigate the benefits of Agile.

One of the team members asked me to explain the difference between an Epic story and a non-Epic story, to help me explain the differences I referred to a very, very good Apple Strudel I ate the night before at a local bar.

I explained that if you had a family size Apple Strudel that you wanted to eat, would you attempt to eat it in one? or break it up into managable sizes? Hopefully the anwser to this is obvious (for those who it is not, its the second of the two). Now imagine a story that is 'family' sized, too large to 'consume' in one go, which we refer to as an Epic Story, instead of attempting to complete the whole Epic Story in one, you break it up into manageable sizes.

I wanted to share this example with you in case you are fed up with the 'Epic' book / chapters explanation :-)

Tagged as: , , , No Comments
30Jun/110

Amber is heathly, green means we’ve over cooked it and red means we haven’t got a clue

Picking up on Simon Cromarty, aka the Agile Pirate, blog about Yellow is the new Green, I had an additional take on his work, where Yellow (or Amber if you use RAG) is the most healthy status depending on how you use the status.

Is Yellow or Amber used in your business to flag early failure warning? Or could it be used to flag that there is some uncertainty over a work effort? As we are Agile people we don't want to spend to much time on the requirements of our work so that we have every last peice documented. So instead of using RAG / RYG as a measurement of failure, if we rework this would could have it measure a teams uncertainty around a story;

  • Green - Over cooked, too much time spent on defining the story
  • Amber / Yellow - We know enough to be able to flag that we know a fair bit but that there's still some undefined areas
  • Red - We haven't got a clue and are screaming for help
Tagged as: , , , No Comments