People10 ‘Total Agile’ software development environment

Here is a glimpse of our new ‘Total agile’ office… Will add more pics as we go…

In our open agile environment, you wouldnt see people hiding in isolation behind the walls.. There is always buzz and energy on the floor. There are debates and huddles and movement..

when we are in the mood to ideate, we take along our color pens and our buddies and scribble stuff on our walls everywhere.. we could work from next to our coffee machine (yes we are wired as well as wireless everywhere), or we huddle on our bean bags in the break-out space.. yes we are connected there too..  If at all we need some alone time with our laptops, thats possible too, we just need to move into one of the kiosks…

Agility wouldt be possible without the right infrastructure. so we have powerful machines with wide screens and powerful servers virtualised to run any number of environments.. we create and drop them on the fly..we check-in, integrate, test, and deploy, all in matter of minutes.. we research, ideate and invent.. we dont have many rules when it comes to work, ‘execution’ and ‘teamwork’ is the mantra and creativity RULES !!!

Friends, would love to hear your comments or questions !


Never miss a story!

Sign up for our newsletter and get the best stories delivered to your inbox.

Co-founder of People10, a 'total agile' software development and consulting company


  1. S.SrinivasaraoReplyFebruary 13, 2012 at 9:38 am 


    • ZoeReplyMay 9, 2012 at 5:53 am 

      What I like about this post is that it gives parity to the various types of thinking and encourages us to see Agile as part of a wider toolkit, rather than something that we do’ exclusively to the exclusion of all others. In doing this it discourages the tendency towards a dogmatic or ideological application of Agile’ It is all to easy to say to account for things by saying, It’s because we’re [doing] agile’ rather than giving a meaningful explanation for the thinking behind our actions.

  2. pozycjonowanieReplyFebruary 18, 2012 at 9:10 pm 

    Magnificent submit, very informative. I wonder why the opposite specialists of this sector do not notice this. You should proceed your writing. I am confident, you have a huge readers’ base already!|What’s Going down i am new to this, I stumbled upon this I have discovered It positively helpful and it has aided me out loads. I am hoping to contribute & help different customers like its helped me. Good job.

    • Nisha ShoukathReplyFebruary 19, 2012 at 3:05 am 

      Thanks a lot, pozycjonowanie ! Not sure about huge reader’s base as I started very recently. I am very happy to know that its helping you, and would be eager to know which sections you percieve to me most useful so that I can write more in detail about it. Thanks again and pls feel free to share the link with others. Cheers and take care !

  3. Ratna DeoReplyFebruary 27, 2012 at 6:06 am 

    Do you follow automated/semi automated continuous deployment ?Or release happens as end of each sprint ?No doubt continuous integration and deployment are key for success with a good tech team ofcourse .Not sure what all tools you are using …but nice to see it

    • Nisha ShoukathReplyFebruary 27, 2012 at 7:17 am 

      Thanks Ratna
      Yes, we follow completely automated deployment pipeline with automated unit tests, integration, acceptance tests, smoke tests, undeploys/rollbacks, and push button deploys. Jenkins is what we use now..
      A glimpse of one of our active pipelines here :

      • Ratna DeoReplyFebruary 27, 2012 at 7:53 am 

        Awesome .I have also been using this with little modification – like code review and some manual test (Manual intervention is evil but code review is must IMO ) .We setup around jenkin and atlassian tools (like jira and crucible)

        • Nisha ShoukathReplyFebruary 27, 2012 at 8:00 am 

          Cool ! I agree. We use some code review tools as well. If you dont mind, could you pls give me some insight into which company you work for and what is the nature of the project. It would also be interesting to know the frequency of production releases.

          • Ratna DeoFebruary 27, 2012 at 8:13 am 

            I work as remote employee for austin based .I work on continuous integration (and tools development to make it work ) and other development related tools and if time permits then grails/java development .

            Pre-production(staging) code release frequncy is 5-10 times a day .Production release happens once a day at least.

  4. SUMAN MITRAReplyMarch 6, 2012 at 3:37 pm 

    How do you manage legacy java application enhancement using agile (XP)? Mostly for unit testing, what measure do you take whether it will not hamper existing functionality?


  5. Sunish ChabbaReplyMay 31, 2012 at 3:04 pm 

    I’ve read a few of your blog posts but somehow missed this one and stumbled upon it today. The work environment is simply great and can be considered as Holy Grail of Agile development.

    Kudos, keep it up.


Leave a Reply

Your email address will not be published. Required fields are marked *

2  ×  5  =