Skip to main content

Agile model for developing device drivers

Last post 05:59 pm June 26, 2015 by Charles Bradley
2 replies
12:08 pm June 23, 2015

I have read many stories of Agile model applied to web related projects. Has anyone come across stories of Agile model applied to device driver development? Can anyone share such stories? What are the learnings?


05:21 pm June 25, 2015

Hi,

I have written device drivers in the past but not using an Agile model. This is an interesting one because depending on the hardware that you are driving you already have a fixed set of functionality more or less and so may not have to deal with change so much, unless the hardware is a prototype and still evolving!

You can build this up nicely in stories, just start creating the basics and adding each new operation as a feature

System hardware detection
Device sign on (manufacturer, type, revision)
Device open
Device close
Device remove
Device enable
Device disable

...start adding features for i/o operations that provide a useful function to the end user. They are all features...


05:59 pm June 26, 2015

Jugari,

Check out http://ScrumCaseStudies.com -- definitely the Intel case study has hardware/software combos, but probably other case studies do as well.

In addition, the Large Scale Scrum books written by Larman/Vodde are primarily based on their experiences of doing Scrum in dozens of teams doing embedded dev.


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.