#peopleware

What really motivates individuals. The Agile Manager (2)

Try to google “what motivates employees”, and you get such a high number of responses you can spend the rest of your days figuring this mystery out.

If you want a light summary, check out Science Direct. If you want more, you can always get the books and read each author’s perspective (I tend to do that, which explains why I only write blog posts once in blue moon).

In this post, I’ll briefly…

New Post has been published on https://freebookzone.download/peopleware-productive-projects-and-teams/

Peopleware: Productive Projects and Teams

Peopleware: Productive Projects and Teams

  Few publications in processing have experienced as deep an impact on application supervision as Peopleware . The initial understanding of the long-time best-seller is the fact that the important troubles of software-development are individual, not specialized. They’re difficult concerns; but resolve them, and you’ll increase your odds of success.

  “Peopleware has always been among my two beloved publications on application design. Its fundamental power is its foundation of tremendous true expertise, a lot of it quantified. Several, many assorted initiatives happen to be shown on and distilled; but what we’re presented isn’t only deceased distillate, but stunning cases that we discuss the authors’ inductions. Their idea is right: many application task difficulties are sociological, not technical. The ideas on crew jelling and work place have improved my thinking and coaching. The next variation gives power to strength.”

— Paul G. Brooks, Jr., Kenan Professor of Compsci, College of New York at Chapel Hill, Writer Of The Legendary Man-Month and The Style of Design

“Peopleware is the main one guide that everybody who operates a application crew must study and reread one per year. Within the quarter-century considering that the first-edition seemed, it’s be more crucial, not less, to consider the cultural and individual troubles in application develop¿ment. This is actually the only method we’re likely to create more gentle, profitable locations. Get it, study it, and retain a available at work offer closet.”

—Joel Spolsky, cofounder, Pile Overflow

“When a guide in regards to a industry as unpredictable as application style and use reaches a next variation, you may be sure the creators create of serious concept, of the essential triggers for what we viewers encounter, and not of the outer lining that everybody understands. Also to carry people, precise humans, in to the blend! How outstanding. How scarce. The creators have produced this next edition, having its upgrades, solely terrific.”

— Devin and Ron Austin, coauthors of The Spirit of Layout and Artistic Making

El tema humano avanza cada vez más en el mundo del software, pero no es un tema que sea nuevo, sino que es muy antiguo del que podemos encontrar mucha bibliografía. En este #devHangout, Noemí nos contará su experiencia, destacando lo que más impacta en un equipo y cuales son las claves principales para gestionar un equipo de desarrollo software.

Invitada: Noemí Navarro Sánchez

Actualmente colabora en 233 Grados de TI - Comunidad, apasionada por las metodologías ágiles y calidad software y es Ayudante de Investigación en la Universidad Rey Juan Carlos.

En este #devHangout tratamos los siguientes puntos:

Introducción

Conceptos de equipo de alto rendimiento

Libros recomendados sobre Peopleware

Los tipos de Management

Características de los equipos eficientes

Características de los equipos eficientes

Buscar a los miembros más adecuados y retenerlos

Trabajar en un equipo de productividad

Conocer el impacto de la no calidad

Pequeños

Multifuncionales

Experiencias y técnicas

Niko - Niko

Kudo Box

Mob Programming

Enlaces recomendados

http://www.javiergarzas.com/2015/12/el-management-1-0-el-2-0-y-el-3-0-y-la-complicada-situacion-hoy-de-muchas-organizaciones.html

http://www.javiergarzas.com/2012/07/equipo-agil-auto-organizado.html

http://www.javiergarzas.com/2013/05/interrumpir-productividad.html

https://www.youtube.com/watch?v=o90o6Oassec

Compartimos el video del #devHangout:

Sponsors:

Agradecemos a GetonBoard por ser sponsor del #devHangout. La empresa PC Miraflores, necesita un Web Designer Junior full-time en Lima con conocimientos en  MySQL, PHP, Adobe SuiteWeb, design.

Agradecemos a Sinergia por ser sponsor del devHangout, Sinergia es una empresa ecuatoriana, especialista en Desarrollo de Aplicaciones Móviles, más información en http://sinergiass.com/aplicaciones-moviles/ 

Sobre devAcademy:

En devAcademy creamos lo que creemos y creemos en comunidad y en la mejora constante, estos son nuestros servicios:

Desarrollo de Software: Transformamos tus ideas en productos centrados en el usuario de forma ágil, colaborativa y sin importar dónde te encuentres. Nuestro fuerte son las aplicaciones web y móviles.

Some more thoughts on open floor plans.

While I can absolutely manage to work in such places I’ll be happy to admit that I don’t think they improve efficiency all the time.

I think that taking one full month between releases is too long as it’s really frustrating to receive feedback (especially negative) on the old version of your application:- Your app is great, but the fact that X isn’t working turns me off.- Thanks. We’re aware of the issue and already fixed X. Just wait for the new update.

We’ve got to strive to do at least one release a week. To accomplish that, we have to be super disciplined about cutting out unnecessary features. Don’t try to load as many things as possible in the new update. Add one atomic component, test it thoroughly and send it to App Store. While they’re taking their time to approve the app, we can work on the next update. It’s also great for morale knowing that you saved your progress.

Prioritize the things you’re going to work on based on the following ratio u / t, where u is the utilitarian importance of the feature, t is the time it takes to implement it. No overthinking, very simple. For example, if it takes a week of the client work to create the floating separation between morning and evening rituals in the daily rituals list, toss it. That feature has zero utility even if it took you an hour to code.