embeddedincork.net

ng-embedded.blogspot.com

Timo's weblog: See you in Boston

http://ng-embedded.blogspot.com/2010/09/see-you-in-boston.html

Anatomy of One Agile Development Experience. See you in Boston. I'll be attending ESC 2010 in Boston in a couple of weeks. You can catch me speaking. About embedded agile on Tuesday 21st. You can find me somewhere in the conference throughout the week. Let me know if you're around. Subscribe to: Post Comments (Atom). Come up to the lab. Agile Hardware and Co-Design, Agile2011. Embedded Test Cycle - the First 3 Years, Agile2011. Embedded Agile Paper, ESC2010. Embedded Agile Slides, ESC2010.

ng-embedded.blogspot.com

Timo's weblog: 09/2011 - 10/2011

http://ng-embedded.blogspot.com/2011_09_01_archive.html

Anatomy of One Agile Development Experience. Slides from Agile 2011. Agile 2011 ended in Salt Lake City, Utah a few weeks ago. It was again great to meet the growing circle of friends in agile community. This year my own conference was a bit different as I submitted two talks and participated in the review process for Agile for Embedded Systems Development -track. You can find my slide decks via the links below:. Embedded Testing Cycle - the First 3 Years, Markku Åhman and Timo Punkka. Come up to the lab.

ng-embedded.blogspot.com

Timo's weblog: 10/2012 - 11/2012

http://ng-embedded.blogspot.com/2012_10_01_archive.html

Anatomy of One Agile Development Experience. Invasion of Agile Hardware at Design East, Boston. Topics around Agile Development have slowly but steadily been making their way into Embedded Systems Conference program. Couple of weeks ago Design East in Boston. Had several sessions on Agile Development, but most noticeably 3 talks on Agile Hardware. One of them by yours truly. You can find the slides and technical paper associated with it via these links ( slides. Subscribe to: Posts (Atom).

ng-embedded.blogspot.com

Timo's weblog: Fiddling around before TDD

http://ng-embedded.blogspot.com/2010/08/fiddling-around-before-tdd.html

Anatomy of One Agile Development Experience. Fiddling around before TDD. The first of the Uncle Bob's Three Rules of tdd. 1 You are not allowed to write any production code unless it is to make a failing unit test pass. I will share a short story:. But when you start sculpting the solution towards production code, you should take a fresh start and drive test-first based on your newly acquired knowledge. I know I will next time. Subscribe to: Post Comments (Atom). Come up to the lab. Embedded Agile Slides...

ng-embedded.blogspot.com

Timo's weblog: Learning to cope with legacy C

http://ng-embedded.blogspot.com/2009/02/learning-to-cope-with-legacy-c.html

Anatomy of One Agile Development Experience. Learning to cope with legacy C. New responsibilities during the past year have been a great learning experience. The key learning is that now I really know how incompetent I am. I can’t wait to move again and learn how many more things I do really badly, or what would be even better, can't do at all. This is a brief story of one such finding during this joyrney. For the past year we have focused on ATDD. What's different with the latest tests then? For(; ) {.

ng-embedded.blogspot.com

Timo's weblog: 10/2013 - 11/2013

http://ng-embedded.blogspot.com/2013_10_01_archive.html

Anatomy of One Agile Development Experience. My Hardware and Co-Design talk at Scrum Gathering. Couple of weeks ago I attended my first Scrum Gathering in the city of light, Paris. On the first day I was offered an opportunity to present my Hardware and Co-Design talk. You can find the abstract below, and slides are available here. Come to this session to get the practitioner’s view on using Scrum beyond embedded software development. Agile software development is getting more and more attention also in ...

ng-embedded.blogspot.com

Timo's weblog: Agile Hardware - Support from a Surprising Source

http://ng-embedded.blogspot.com/2015/03/agile-hardware-support-from-surprising.html

Anatomy of One Agile Development Experience. Agile Hardware - Support from a Surprising Source. 8220;Agile development may be suitable for software development, but for hardware development we have to use something more formalized and waterfall just works for this”. Some time ago I stumbled across the above comment. I can’t disagree more. Second, the N&N paper, which inspired Scrum framework for software development, did not talk about software development. The case projects developed copiers, camera...

ng-embedded.blogspot.com

Timo's weblog: Coverage with lcov, and so what?

http://ng-embedded.blogspot.com/2009/06/coverage-with-lcov-and-so-what.html

Anatomy of One Agile Development Experience. Coverage with lcov, and so what? A while back we ran an experimental line coverage analysis on our acceptance test suite. The result was 68% on the code for the main control board. I got the result from nightly build and mentioned it in Daily Scrum, and prompted "so what do we think about it, should we track it"? Everyone on the team had a blank stare and then finally a team member came forward "yeah, that's a good question. So, what? I started with acceptance...

ng-embedded.blogspot.com

Timo's weblog: 12/2011 - 01/2012

http://ng-embedded.blogspot.com/2011_12_01_archive.html

Anatomy of One Agile Development Experience. Earlier I wrote about the long distance I went with mac driver design ( link. There is no need to make tradeoffs and large/long changes without feedback because of lengthy burning times, or lengthty stepping path to debug newly written code. I think what I experienced is well explained by Michael Feathers in his talk "The Deep Synergy Between Testability and Good Design" ( video. The original design was done with just testability in mind. At that time ther...