This aligns directly with my experience at my previous job. We had SCRUM teams working on product development, and tried to integrate service maintenance into that same model. What is the most important task to work on one day w.r.t. service may very well change the next day. We didn’t try Kanban, but I did begin discussing its potential for managing our maintenance portion of our business.

I would like to find a way to inform users why hardware does not pass certification or has been stop from being certified. I will put some thought into that.

Thanks,

Victor

I’m still concerned about the certication story and thus the utility to end-users as part of the retail/usage lifecycle when it comes to OS upgrade path.

Take for example this laptop:
http://www.ubuntu.com/certification/hardware/200804-253

Why didn’t this laptop pass certification for 11.04 or beyond? Can the website actually start pointing to why previously certed hardware failed cert on newest OS as a starting point for some community self-service for continued hardware enablement. I’m not saying you can garuntee the future, that’s the OEMs job , but pointing out technical reasons and bug reports for cert failures for already cert’d systems might help the community fill in the gaps and get the hardware re-operational even if you don’t cert it.

-jef

about the improvements, I have sent you an email so you can send me the file

I did find the icons confusing: both the Canonical and the Ubuntu icons look pretty official. Yes, a mouse-over shows the difference, but I doubt everyone will do that to discover what the icons represent. Perhaps somewhere on the page a key to what they mean could be placed.

Also, there are some generally minor English language errors. Since I edit for a living, I did a quick edit to clean it up a bit. I can’t program so there isn’t much else I can do to contribute to Ubuntu! Anyway, if you’re interested let me know how I can send the file to you. (I won’t be offended if you’re not.)