|
Waterfallish Agile.
Waterfall for the hardware part. Agile for the software part.
|
|
|
|
|
Well I think the problem is Software want the hardware to change to meet there demands. At times we have had ARM9 used in place of a PIC for controlling some LED's... I mean come on that is plain overkill!
|
|
|
|
|
Is that like dancing in between the raindrops?
|
|
|
|
|
Amarnath S wrote: Waterfooallish Agile.
FTFY 
|
|
|
|
|
|
Cheers, but its not really resources that are the problem...
|
|
|
|
|
Better not to think of them as one project.
The second project (software) needs to wait until the first project (hardware) is ready for a release.
|
|
|
|
|
glennPattonWork wrote: Its just that AGILE doesn't seem to be applicable for hardware.
Well, if you have unlimited financial resources and time, the AGILE works great for hardware too.
Oh wait, it only works that way for software too. 
Latest Article - A Concise Overview of Threads
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
glennPattonWork wrote: which is fine for software
This is plain wrong. It is *possible* for software, but it does not make it *fine*.
Agility does not mean you can handle changes until last minute (There is no time machine sold with the Agile manifesto package). Agility means that your organization is capable of optimally cope with changes - refusing a change that comes too late for a deadline is also a perfectly *good* way to handle a change.
|
|
|
|
|
Oh boy. Trying to fit a square peg into a round hole. Either the square peg need to be shaped to round or the round hole need to cut into square. I understand your dilemma. The hardware is a square and you want to be catchy round process. Don't fight it mate. Keep them separate. 
|
|
|
|
|
If you find one, please let me know. I work for a hardware company, managed by hardware engineers.
"By God, those flaky software monkeys will learn how to manage their projects just like hardware! There will be processes, appropriate documentation (and we decide what's appropriate), and they will write Engineering Change Orders (ECO's) for every single update. No more of this seat-of-the-pants willy-nilly updating!"
Not an exact quote, but you get the gist  .
Software Zen: delete this;
|
|
|
|
|
The key question in all these techniques is "What is the key constraint, or freedom, that stops / allows work to proceed?". It's all about the [theory of] constraints, e.g. Eli Goldratt, 'The Goal'
In agile it is the realisation that the manufacture cost (running the compiler) is almost zero, so one can concentrate on the other problem - do we know what we want, i.e. continuously ask the customer if the product is what was expected.
For the Circuit board design, the layout of the board is a time constraint, along with knowing if the customer has their external circuitry stabilised (there it's about the interface(s)). So concentrate on getting the time killer (and or cost / quality killer) right.
All in all, the best development strategy is to engage the brain, learn from others, and avoid blindly copying the many misunderstood fanboy techniques. There are no silver bullets (see “The Balle-Argentee Method.”).
|
|
|
|
|
I'm not sure why a conventional agile strategy won't work. You can turn a board in a week using an out-of-house shop. It's not the 1980s any more.
|
|
|
|
|
1. Use your head.
2. Look at the original agile principles (not the myriad of implementations).
3. Look at the underlying principles in Kanban and waterfall.
4. Consider an underlying strategy that made NASA's moon landing project and the US Navy's Nuclear Power Program so successful - value engineering.
5. Once you understand the principles of various methods, come up with a strategy for managing and development of projects that fits the needs (as opposed to trying to change the need to fit some process). What works for hardware does not have to work for software. Adapt and overcome.
|
|
|
|
|
Until the API's have been "fixed" and the software is talking to the hardware, things are out of control.
And anytime the 2 stop talking, things are out of control.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
I used to work for Itel. Their production mainframe boards were all wired, no land patterns other than power. It was not difficult to spec wiring changes at any time.
|
|
|
|
|
Paddy gets arrested for assaulting his wife.
The judge asks him "why do you keep beating her?"
"Not sure judge, but I think it's got something to do with my weight, longer reach and superior footwork."
|
|
|
|
|
1980s - reader laughs.
2018 - reader gets a visit from HR for just reading it.
|
|
|
|
|
Didn't read your article, but I know this is the KB you are referring too. Wasted 1.5 hours of my life yesterday trying to figure out why a customer all of a sudden couldn't access his network shares.
Anyway figured it out, uninstalled it and was gonna post something here but got home too late and thought elephant it, you lot can figure it out for yourselves.
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
I installed updates last night on my Linux desktop, and didn't loose any network shares as a result.
Just thought I'd mention it...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I installed updates on my linux desktop [many times] and was never forced to reboot.
Message Signature
(Click to edit ->)
|
|
|
|
|
I'd rather take the occasional reboot, as opposed to being prompted nearly daily by my Linux VMs for updates.
OTOH, yeah--that Win7 update that breaks network shares is rather inexcusable. The scenario isn't so uncommon this shouldn't have been caught. It's official, nobody at MS these days does any appreciable amount of testing.
|
|
|
|
|
John Simmons / outlaw programmer wrote: I installed updates last night on my Linux desktop, and didn't loose any network shares as a result.
Just thought I'd mention it...
Yeah, but I didn't install any updates that caused me problems, it was a customer at work.
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
John Simmons / outlaw programmer wrote: didn't loose any network shares as a result.
But it broke your spellchecker?
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
FWIW, I uninstalled the patch from the 2 systems that had it, but network connectivity between them wasn't restored.
One of these systems is rather vital to me, so instead of waiting for MS's solution, I ended up migrating all the files under the local admin account (which is affected) to a domain account (which isn't) - this is something I had meant to do for a good while anyway.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
