#lean development

[techenthuinsights]

Lean app development is a quickly emerging strategy for software development that brings the swiftness and power of agile software developme

[alphataurus-in]

Maximizing Efficiency with Lean Development

Introduction In today’s fast-paced business environment, companies need to be agile and responsive to stay ahead of the competition. This is where lean development comes in, a methodology that focuses on efficiency and value creation by eliminating waste and maximizing resources. In this article, we’ll explore the principles of lean development and how they can be applied to agile project…

View On WordPress

[faisalakhtar12]

How You Can Turn a Short Developer Assignment Into a 9-Year Job

How You Can Turn a Short Developer Assignment Into a 9-Year Job

“The man who has the remedy for a toothache will always be rich.” — my grandfather

Have you ever had a toothache? I am not talking mild discomfort, but the kind that radiates from your jaw to your brain and through the rest of your body. I have, and let me tell you, I would have done anything to get rid of that pain. It is near impossible to sleep and there is absolutely nothing you can do…

View On WordPress

[wjackman]

Following the Path of the Lean Startup

Following the Path of the Lean Startup

Over the past year or so, I’ve talked about the need to follow the path of the Lean Startup, as described by Eric Ries in The Lean Startup. But how well are we following that path? In the simplest terms, Lean Development is:

“…a systematic process for iterating from Plan A to a plan that works, before running out of resources.” (Ash Maurya, Running Lean).

That sounds easy enough and sounds like…

View On WordPress

[wjackman]

Patent Pending

Recently we’ve come up with a really good idea for the application. In fact, it’s a bloody…

View Post

[metapundit]

Beware the Vanity Metric

As the Hypergrid grows, we should be wary of vanity metrics.

I'm a pretty big fan of the Lean Business model pioneered by Eric Reis (of IMVU fame).  The main concept behind Lean is that you start small, release a barebones version of your product, measure carefully, and then modify the product based on feedback. Rinse and repeat until you succeed, give up, or decide things need to radically change.  Critical to that process is knowing what's the right metric to measure.  It's very tempting to measure what Eric calls "vanity metrics" such as user registrations, or number of posts. 

While these metrics sound impressive and make the creator feel fuzzy inside, they are ultimately pretty useless metrics for figuring out how to make things better once things begin to go wrong.  Metrics like "the average number of posts per user per day" are far more useful, because they let you tap into how your users/customers are actually using the product.

As the Hypergrid and Opensim in general grows, I'm seeing an awful lot of vanity metrics being tossed around as solid indicators of healthy growth.  There's two in particular I want to call out:

  Region Count: It doesn't matter how many regions there are in the Hypergrid or any grid if they're all abandoned 99.99% of the time. 

User Count: I know for a fact I have at least 2 different accounts on OSGrid I've abandoned for various reasons (passwords are hard).  Maybe they still exist, maybe they don't.  But one thing is for sure, they sure don't represent a hyper-engaged user brimming with virtual social vitality.

I'll give Active Users a pass, even though technically it's pretty much a vanity metric.  At the very least it gives you a sense of how "active" (a pretty vague word/concept) grid has been in the recent past.  

This isn't to say we shouldn't share vanity metrics.   They're encouraging to look at, and give us a vague sense of what direction the wind is blowing in.  However, we should learn to differentiate vanity metrics from useful ones and be honest with ourselves about which is which.

[juanpablodm-blog]

Lean Development, aplicado a Startups

 Tips a tener siempre en cuenta.

Eliminar desperdicios (Eliminating Waste), Si alguna actividad podría ser excluida o el mismo resultado podría ser logrado sin ella, esta actividad es considerada un desperdicio.

Amplificar el aprendizaje (Amplifying Learning), Aprendizaje validado, experimentación cientifica e Iteración en los lanzamientos del producto para acortar los ciclos de desarrollo, medir el progreso y ganar valiosa retroalimentación de los clientes.

Decidir lo más tarde posible (Deciding as Late as Possible),  no suposiciones y pronósticos inciertos, más capacidad para el cambio.

Entrega lo más rápido posible (Delivering as Fast as Possible),  TTM, Time To Market.

Construir con integridad (Building Integrity In), refactorizar es mantener la sencillez, la claridad, la cantidad mínima de funcionalidades en el código.

SCRUM

Documentar las users stories en boards como trello.com o similares dividido en secciones, personalmente me gusta la planteada por Juan Pablo Sarquis.

IceBox, lugar para documentar las ideas que aun no se van a desarrollar.

MVP's BackLog, todas las users stories que va a tener el MVP.

Spring BackLog.

In Progress.

Dev Ready.

Done.

Categorizar los labels por funcionalidad en: funcional, management, interfaz grafica, bugs, tecnica.

Escribir las users stories en un lenguaje unificado.

Como [rol] quiero [característica] para [valor de negocio].

Escribir también los requerimientos no funcionales precedido por [NF]. Eje. [NF] Setup de Framework, arquitectura general, git, jenkings, staging, CodeIgniter. Creación de Accesos a todos los miembros a todas las herramientas. 

Fuente y más.

Wireframing, Prototyping and Mockuping: Dibujos que representan una idea ingeniosa.

Wireframe (estructura Alambre): es la información que debe ir documentada. Donde los diseños tendrán en cuenta todos los diferentes elementos de la página necesarios mínimos y que están situadas en la mejor manera posible.

Considerar al momento de crear wireframes, los principales grupos de contenido (¿qué?), la estructura de la información (¿dónde?), la descripción y visualización básica del usuario - interacción de la interfaz (¿cómo?).

USO: Documentación y comunicación rápida.

Una App que recomiendo para IOS: POP - Prototyping on Paper 

Mock-up (maqueta): se centran generalmente en los elementos de diseño visual del sitio. Estos son a menudo muy cerca o idéntica al diseño del sitio final real e incluyen todos los gráficos, la tipografía, y otros elementos de página. Maquetas son generalmente sólo archivos de imagen.

USO: Armar el diseño final para obtener el feedback de los interesados (stakeholders).

Prototype (prototipo): Son diseños de página web semi-funcionales de una maqueta / borrador que sirve para dar una vista previa de mayor fidelidad del sitio real que se está construyendo. Esta etapa precede a la programación de la lógica de negocio del sitio y simula la forma en el sitio con el tiempo va a funcionar.

USO: pruebas de usuario, la espina dorsal reutilizable de la interfaz.

Fuente y más.

  Usabilidad web: Lean UX, Don`t make me think.

[onoffkonoff]

Philosophy and tech startups go pretty well together

I'm a philosophy grad. I mostly cared about analytic philosophy, especially the philosophy of science, but also the philosophy of race. I decided to study philosophy because it seemed to be the closest thing to what I did in high school: argue.

I argued incessantly on forums, chatrooms, comment threads, and my first period sciences sociales class with Mr. Mitchell. I argued there in French, and I did it for 5 minutes a day at least. I tried my damndest to communicate my opinions, and after five years of doing that, I could speak the language pretty decently.

My need to argue has helped me learn a lot of things - including how not to argue, and to instead be fair to someone’s point. But there’s one skill that has become especially important in my life, and which is serving me incredbily well at my new job at a tech startup called GoInstant. It’s the ability to find counterexamples.

Counterexamples In philosophy, especially in earlier classes, basically all you do is analyze an argument until you understand how it fails to account for one very obvious, very important thing: a state of affairs we call a ‘counterexample.’ It’s simply the one state of affairs that shows the argument your interlocutor is making must be inadequate in some way. When Callicles says that the best people are the strongest people, Socrates points out that the masses are pretty strong, and they do some pretty horrible shit. Bam. Counterexample.

The development process is awfully similar, except the states of affairs that you’re hunting aren’t called counterexamples: they’re called bugs. And the uncovering of bugs is the challenge that keeps developers busy.

At GoInstant, we have an unbelievably enormous project: we’ve got to make our software work on the entire web. Every single webpage should work within our browser, and if one doesn’t, we have to figure out how to do make it work, so that that one state of affairs will be covered by our code.

The greatest good for the greatest number Except, of course, it’s not that simple. It’s not just as simple as finding all the bugs, all the states of affairs in which our software doesn’t work. Instead, we must first decide: what is most important? 2nd most? 3rd most? etc. etc. ad nauseum.

There’s a normative project behind every single app that has been ever designed: what matters most, given that we have limited time and money to put towards the project? It is the question that fuels all design decisions, for anything. It is the question whose answer separates great products from awful ones. It is the question I intend to spend the rest of my life answering, because it is that complicated and nuanced and fucking cool to work on.

Good answers for the hardest question This question is a question of what good design really is. There are a lot of answers, but there’s only one way to solve it: find counterexamples. And these counterexamples are states of affairs in which human beings are using an app* and finding it wanting, unable to fulfill its purpose as well as it should (to borrow some more normative terms).

But the complicated thing is that for a design to matter, it also has to be just one thing in an ecosystem of creation: an ecosystem that makes yet more wonderful things. It has to be the product of a deeply talented team, because it’s not easy to make that one thing. It has to generate revenue to power every stage of its development and creation. It’s an organism that’s created and which can give the power to create, and that’s kind of awesome.

Finding a niche It’s also unbelievably rare. If it grows and has any staying power, it is because it occupied a niche that was brought about from the combination of available technology, models of commerce, political dynamics, and social trends at a particular time and place. To read those signs well is impossible; it’s easier to just occupy the time and place and see what it is that you’ll find yourself needing in five years time. That is to say, it’s always a crap shoot.

There’s someone, or a group of someones, in the design process who will have to make the tough decisions about their little organism. They’ll have to see the connections between commerce and possibility and usefulness and human need, the ones who’ll have to tinker with their creation until it fits. After that, they’ll have to do everything they can to make everyone else aware of those connections. That latter part - the making aware of - is called marketing. Everything before it is product management - or intelligent design, if you think of designers as the sort of god figures of this weird ecological analogy.

So what do you do if you have an idea? To turn it into anything important, you need to do more than just make it a physical object or a collection of lines of code. Importance is determined by how it fares. You need to find out where it sits, and you need to get it there. If there is no spot for it, or if it bleeds money while crossing a desert in search of an oasis, then shit. You’re out of luck, this time. I hope you didn’t risk too much, and I hope you can still change it enough so that it can thrive, somewhere. Probably not where you expected, though.

There’s always the rare possibility that you find the spot for your app, and it grows and flourishes and makes everything that nurtured it just all the stronger for having gotten it to this point. It’s not something that happens often, and a lot of the time, it’s less about being the perfect solution than it is about just having been good enough for the time and place. Until, of course, the perfect solution comes along.

There’s a problem with perfect, though. Nothing that evolved has ever been perfect. And no theory is immune to counterexamples. As long as those two things are true, and they always will be, opportunity can be found. Apps can be made, and can thrive. The universe will keep spinning, and entropy will gather in the practiced hands of an unusual, unpredictable force.

*I’m just gonna use app as shorthand for anything that can be used by a person, ever.