Hi Brian
What is a good time for a call? I have a call Wednesday 9-10AM CT.
Hours that generally work well for me are 9AM-3PM CT.
Thanks, James
--------------------------------------------------------------------------
James Grenning - Author of TDD for Embedded C - wingman-sw.com/tddec
wingman-sw.com
wingman-sw.com/blog
twitter.com/jwgrenning
facebook.com/wingman.sw
Cell: +1 847-630-0998
[](http://wingman-sw.com)
On 30 Nov 2016, at 13:04, James W Grenning wrote:
> Great, next week it is.
>
> James
>
> --------------------------------------------------------------------------
> James Grenning - Author of TDD for Embedded C - wingman-sw.com/tddec
> wingman-sw.com
> wingman-sw.com/blog
> twitter.com/jwgrenning
> facebook.com/wingman.sw
> Cell: +1 847-630-0998
> [](http://wingman-sw.com)
> On 30 Nov 2016, at 12:35, Brian Monson wrote:
>
>> James,
>>
>> Next week would be excellent, let's talk on the phone about what you
>> provide and what makes sense for Cirque and see what we can do to get
>> some
>> training from you. Thanks for getting back to me so fast, looking
>> forward
>> to hearing from you next week.
>>
>> Best Regards,
>> Brian
>>
>>
>> [image: cid:[email protected]]
>> <http://www.cirque.com/>
>>
>> *Brian Monson*
>> Chief Operating Officer
>> *[email protected] <[email protected]>*
>>
>> SkypeID: brian.monson.cirque
>>
>> 2463 South 3850 West
>> Salt Lake City, UT 84120
>> *Office:* (801)467-1100 x 3118
>> *Cell:* (801)231-4630
>>
>>
>> On Wed, Nov 30, 2016 at 11:27 AM, James W Grenning
>> <[email protected]>
>> wrote:
>>
>>> Hello Brian
>>>
>>> Thanks for contacting me. I am in Europe this week. Are you
>>> available for
>>> a call next week? We can discuss your needs and we can discuss how
>>> we can
>>> help. Below is some other info on my background, company and
>>> services.
>>>
>>> Thanks for buying my book!
>>>
>>> James
>>> My background
>>>
>>> I got involved in applying Extreme Programming to embedded software
>>> in
>>> 1999, twenty years into my career. I immediately saw the potential
>>> for the
>>> practices and principles to really help with embedded development. I
>>> was
>>> fortunate to put the techniques into action with one of my clients
>>> at the
>>> same time. From my experiences, I started writing and speaking in
>>> conferences about how to adapt and apply the techniques to embedded.
>>> It
>>> also led to the writing of my book Test-Driven Development for
>>> Embedded C
>>> <http://wingman-sw.com/tddec>.
>>> Wingman Software's Focus
>>>
>>> These are the areas that we spend most our effort. You can find more
>>> information below. Drill deeper by following the links.
>>>
>>> - Helping organizations (product management, engineering, QA) get
>>> started on the iterative and incremental delivery and planning.
>>> - Helping people, teams and organizations get started with Agile
>>> engineering practices, including TDD, refactoring and design.
>>> - Technical workshops where we work with you to solve challenges
>>> in
>>> your product and code:
>>> - Follow on coaching for experienced teams and organizations to
>>> get to
>>> the next level.
>>>
>>> Time spent in my training and workshops help you greatly reduce the
>>> guess
>>> work on how to apply these techniques to your challenging
>>> environment. I
>>> can also offer an overview session for your executives, managers,
>>> and other
>>> non-engineering people.
>>> Agile startup workshop
>>>
>>> Instead of spending three days learning Scrum or Agile planning
>>> practices
>>> with made up problems, we use your product. Getting started in your
>>> own
>>> product is a challenge, especially for embedded systems. Most the
>>> Agile
>>> material for stories and planning are around IT systems, not leaving
>>> much
>>> help for the embedded developers. Our Agile Startup Workshop is
>>> designed so
>>> that your team will be ready to start iteration one.
>>>
>>> - Agile Startup Workshop
>>> <http://wingman-sw.com/workshops/agile-startup-iteration-zero>
>>>
>>> TDD training approach
>>>
>>> After convincing myself that TDD was a very fun, flexible and
>>> productive
>>> way to work, I thought others would see TDD and want to adopt it. I
>>> was
>>> wrong. Change is hard and change for no apparent reason is
>>> pointless. TDD
>>> by itself is a solution to a problem. If the problem is not
>>> identified and
>>> agreed to as important, why bother with TDD. My training is for
>>> engineers
>>> that see defects found late in the development effort as a problem
>>> to be
>>> solved. TDD is not a debugging practice, it is defect prevention. It
>>> helps
>>> you go faster, and keep the pass of development consistent.
>>>
>>> You can not learn a new skill just by reading about it. You have to
>>> try
>>> it. Our most popular offering consists of two parts: two days of
>>> planned
>>> training activities followed by a two day workshop in your code.
>>> From
>>> Monday and Tuesday we go through a series of
>>> presentation/exercise/discussion
>>> sessions focussed on the techniques and tools of test-driven
>>> development.
>>> In the exercises, attendees build TDD and unit testing skills on top
>>> of
>>> their existing programming and problem solving skills. Wednesday and
>>> Thursday we usually *Mob Program* and to get some of your code into
>>> the
>>> test harness. Then we form small groups, and work on code that each
>>> matters
>>> to each individual. The goal is to prepare each participant so they
>>> can
>>> continue using TDD and unit testing the day after the workshop. We
>>> work on
>>> what is important in those two days. That may be adding tests to
>>> existing
>>> legacy code that needs to be changed or test-driving new code and
>>> resigns.
>>> It is not 4 days of training, it is two days of training followed by
>>> two
>>> days back to work with our guidance.
>>>
>>> It is a challenge to get started with TDD. The workshop goal is to
>>> move
>>> TDD from the classroom into your challenging product code
>>> environment.
>>>
>>> - Engineering Practices Overview
>>> <http://wingman-sw.com/training/engineering_practices>
>>> - Test-Driven Development for Embedded C Training
>>> <http://wingman-sw.com/training/tdd-embedded-c>
>>> - Test-Driven Development for Embedded C++ Training
>>> <http://wingman-sw.com/training/tdd-embedded-cpp>
>>> - TDD for other languages and environments: Java, Android, C#
>>>
>>> Technical workshops where we work with you to solve challenges in
>>> your
>>> product and code:
>>>
>>> - Legacy Code Workshop
>>> <http://wingman-sw.com/workshops/legacy-code>
>>> - New Code Workshop
>>> <http://wingman-sw.com/workshops/walking-skeleton>
>>> - Design Workshop <http://wingman-sw.com/workshops/design>
>>>
>>> Training strategy
>>>
>>> There are two approaches we've found to help companies adopt TDD.
>>>
>>> 1. Team by Team approach - to get everyone on the same page, have
>>> teams trained together.
>>> 2. Leaders first approach - if you want to touch many teams, send
>>> a
>>> couple respected technical leaders to the training from many
>>> groups. Have
>>> them lead the way to team adoption by learning TDD and
>>> discovering how it
>>> works in your environment.
>>>
>>> Coaching on planning and technical practices
>>>
>>> - Coaching <http://wingman-sw.com/coaching>
>>>
>>> What People say about our services
>>>
>>> - Training feedback <http://wingman-sw.com/training_feedbacks>
>>> - Workshop feedback <http://wingman-sw.com/workshop_feedbacks>
>>> - Testimonials <http://wingman-sw.com/testimonials>
>>> - Stories <http://wingman-sw.com/stories>
>>>
>>> Resources
>>>
>>> - Agile Embedded Software - Paper
>>> <http://wingman-sw.com/articles/agile-embedded-software-development>
>>> - Test-Driven Development for Embedded C
>>> <http://wingman-sw.com/articles/test-driven-development-for-embedded-c>
>>> - Test-Driven Development for Embedded C - Book
>>> <http://wingman-sw.com/tddec>
>>> - Test-Driven Development for Embedded C++
>>> <http://wingman-sw.com/articles/test-driven-development-for-embedded-c-plus-plus>
>>> - Agile Startup - Iteration Zero
>>> <http://wingman-sw.com/articles/agile-embedded-requirements-estimation-and-planning-iteration-zero>
>>> - Story Testing - Executable Use Cases - Paper
>>> <http://wingman-sw.com/articles/story-testing-embedded>
>>> - My other papers can be found here
>>> <http://wingman-sw.com/papers/titles>
>>> - Numerous related articles are on my blog
>>> <http://blog.wingman-sw.com/>
>>>
>>> ------------------------------
>>> James Grenning -- Author of Test-Driven Development for Embedded C
>>> <https://wingman-sw.com/test-driven-development-for-embedded-c-book>
>>> <http://www.wingman-sw.com> wingman-sw.com
>>> blog.wingman-sw.com
>>> @jwgrenning <http://twitter.com/jwgrenning>
>>> facebook.com/wingman.sw
>>> Mobile: +1 847-630-0998
>>>
>>
>> --
>> This message and any attachment are confidential. It may also be
>> privileged
>> or otherwise protected by work product immunity or other legal rules.
>> If
>> you have received it by mistake, please let us know by e-mail reply
>> and
>> delete it from your system, you may not copy this message or disclose
>> its
>> contents to anyone.
>> Cirque Corporation
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.