hahaha, that's a good one, remember seeing it a long time ago, i saved it now.
On Mon, Jun 13, 2016 at 10:29 AM, Hugo Slabbert <h...@slabnet.com> wrote: > > On Mon 2016-Jun-13 08:52:41 -0500, Possamai Rafael via NANOG < > nanog@nanog.org> wrote: > > This may not be an answer very specific to your problem/question, but if >> you take a look at the following image, you will find a summary of what >> they called the engineering design methodology: >> >> >> http://www.cdn.sciencebuddies.org/Files/5083/9/2013-updated_engineering-method-steps_v6b.png >> > > Seriously thought initially that you were going to link to: > > > http://i2.wp.com/tamingdata.com/wp-content/uploads/2010/07/tree-swing-project-management-large.png > > You can adapt it to your circumstances, for example: instead of defining a >> problem in step 1, you can define a product, and after knowing what is >> expected from that product, you can then move to background research, etc. >> >> Hope that helps. >> >> >> Rafael >> >> > -- > Hugo Slabbert | email, xmpp/jabber: h...@slabnet.com > pgp key: B178313E | also on Signal > > > >> >> On Sun, Jun 12, 2016 at 8:52 PM, Kasper Adel <karim.a...@gmail.com> >> wrote: >> >> hi, >>> >>> I am asked to build a large lab/test it. I'm provided crazy scale numbers >>> for lots of technologies (L*VPN, IPv*, IGP*, All Tunnels flavors...etc). >>> >>> It took me a lot of time to build this lab, because when I got the >>> request/test plan handed over to me, I did not verify that these scaled >>> numbers are even possible, not to mention the combination. I assumed some >>> thought/research were done before. >>> >>> I'm trying to put together a list of the lessons learned, and the right >>> way >>> to do this for future reference, specially that this project was time >>> critical and I got beaten hard because I did not deliver on time. >>> >>> So my question is, in your extensive experience, what is the right >>> method/approach to this kind of task: >>> >>> 1) Get started immediately (MVP), things will break, tune it along the >>> way. >>> 2) Do some planning and research first. >>> >>> I'd appreciate any references to 'software engineering' or other >>> industries/ >>> >>> Thanks >>> >>>
