August 5th, 2016
Year 2016 is special for Eclipse users and community in India – we have the first ever conference focused on Eclipse Technologies, Eclipse Summit India, scheduled for Aug 25th to 27th in Bangalore at the Hotel Chancery Pavilion. Eclipse Summit India is being organized in collaboration with the Eclipse Foundation and will feature some of the best speakers from the past EclipseCon conferences around the world.
In 2010, we organized the first “Eclipse Day” – a day for the Eclipse community in Bangalore to get together and share expertise. We still remember that day at a small but cozy hotel on Infantry Road in Bangalore, when we kicked off the very first “Eclipse Day” in India. We followed the tradition in 2011, when SAP came forward to organize it in their campus. There were two more Eclipse Day editions in Bangalore in subsequent years – one organized at IBM and the other one at BOSCH. Each year we raised the bar in terms of content as well as participation. Thus the idea of Eclipse Summit was born!
The conference is spread across 3 days – Thursday, Friday and Saturday. Day-1, Thursday, is dedicated for pre-conference paid workshops. We have lined up 4 workshops by technical leaders in Eclipse space in some of the key Eclipse technologies – Eclipse IoT, Eclipse e4 Platform, Eclipse JDT and Eclipse Modeling Framework. The next two days are dedicated for conference tracks – we have two tracks each on Friday and Saturday. On each of the days, we kick off the proceedings with keynotes by thought leaders in the Industry.
On Friday, we are privileged to have Mike Milinkovich, Executive Director of Eclipse Foundation deliver the Keynote. On Saturday, we have two keynotes – Sumit Rao, VP of Engineering at Cerner Corporation, as the first keynote speaker and Viral Shah, co-creator of the Julia Language as the second keynote speaker. You can find the complete program here: https://confengine.com/eclipse-summit-2016/schedule/rich
Friday Aug 26th, we have two tracks – one focusing on Language Runtime (Java, Node.js, Mobile) and the other on Eclipse IoT Technology. We are fortunate to have leaders from each of these areas – Srikanth Sankaran, whose talks at past EclipseCon were rated amongst the best, will take us through the evolution of Java beyond Java-9, while Benjamin Cabé, Eclipse IoT expert at Eclipse Foundation will unveil the power of Eclipse IoT technologies. These talks are followed by a variety of talks and demonstrations that will expose you to the latest developments and trends in these areas.
On Saturday, the event continues with the focus on language technologies in one of the tracks, while Eclipse Platform focus on the other track. In the language track, Stephan Hermann, Java language guru, will take you through the dynamism in Java language while in the platform track, we have Prouvost, an expert on Eclipse e4 Platform unraveling the mystery of e4. Don’t know what e4 is? Well, now you have a reason to not miss this!
Eclipse Summit India is a conference organized by the Eclipse community for the community. Organizers have done their bit in lining up some of the eminent speakers, who are experts in their own domains. Now it is your, Eclipse community’s – turn, to contribute to it by actively participating to make it a success. Eagerly looking forward to meet you all at the conference!
We’ve last few seats left, register here: https://confengine.com/eclipse-summit-2016/register
January 28th, 2016
Over the last 9 months, our program team of 26 volunteers from 8 different countries have worked together to put together a fantastic program for you.
We got a total of 333 proposals and have selected 108 proposals spread over 10 days.
We are happy to confirm that we’ve 86 Speakers from 18 countries presenting at this very conference.
The team has worked very hard to make sure we’ve a nice balance of topics selected for you at the conference.
Choose from 5 Conferences:
And 16 Pre/Post Conference Workshops:
- Agile Portfolio Management Workshop by Shane Hastie – Mar 14, 9:45 AM – 6:00 PM
- How to Roll Rocks Downhill Workshop by Clarke Ching – Mar 14, 9:45 AM – 6:00 PM
- Agile Engineering for the Web Workshop by James Shore – Mar 14, 9:45 AM – 6:00 PM
- Disciplined Agile In A Nutshell Workshop by Scott Ambler – Mar 14, 9:45 AM – 6:00 PM
- Liquid Organisation Workshop by Stelio Verzera – Mar 14, 9:45 AM – 6:00 PM
- Agile Leadership Academy: Scaling Agile by Sanjiv Augustine – Mar 14, 9:45 AM – 6:00 PM
- Getting2Alpha: Build your MVP faster and smarter with Game Thinking by Amy Jo Kim – Mar 20, 9:45 AM – 6:00 PM
- Lifting Off Workshop by Ellen Grove – Mar 20, 9:45 AM – 6:00 PM
- Test Automation Code Retreat Workshop by Jeff “Cheezy” Morgan – Mar 20, 9:45 AM – 6:00 PM
- Lean Product Development Workshop by Jez Humble – Mar 20, 9:45 AM – 6:00 PM
- Building a DevOps Culture Workshop by Nicole Forsgren – Mar 21, 9:45 AM – 6:00 PM
- Agile Software Development for Distributed Teams Workshop by Jutta Eckstein – Mar 21, 9:45 AM – 6:00 PM
- Large-Scale Scrum Introduction Workshop by Ran Nyman – Mar 21, 9:45 AM – 6:00 PM
- Collaboration Tools Workshop by Michael (Doc) Norton – Mar 21, 9:45 AM – 6:00 PM
- Agile Management – Management 3.0 official training Workshop by Angel Diaz-Maroto Alvarez – Mar 21, 9:45 AM – Mar 22, 6:00 PM
- The Nexus – Scaled Professional Scrum workshop by Steve Porter – Mar 22, 9:45 AM – Mar 23, 6:00 PM
Register here: https://confengine.com/agile-india-2016/register
Agile India 2016 Sponsors
Big thanks to our sponsors for supporting the conference.
We’ve a couple of more sponsorship opportunities available.
August 8th, 2015
Agile India 2014 Conference was happy to host 1236 Attendees from 28 different countries. The attendees belong to 226 different companies and play 342 different roles. More details…
However in Agile India 2015 Conference we hosted 817 Attendees from 26 different countries. The attendees belong to 165 different companies and play 270 different roles. More details…
Also there was a proportionate drop in the number of sponsors. 14 sponsors in 2014 as opposed to 11 in 2015. So many people ask us why the numbers dipped? That’s a fair question. Following are the reasons why we think the numbers dipped:
- We moved from Four 1-day mini-conferences to Two 2-day mini-conferences. (So naturally the count will dip. In 2016, we are back to Five 1-day mini-conferences.)
- In 2015, we shrunk the program team size to 9 members from 29 members in 2014. Reason: we wanted to experiment and see what happens if we don’t decide the team upfront, but add members to the team only based on their contributions (esp. via the Submission System.) I guess that did not work out all that well. In 2016, we are back to a 26 member team that is decided upfront.
- Overall the planning for the 2015 conference was delayed. Only in Sep 2014 we started actively working on the conference. As opposed to starting in July 2013 for the 2014 conference. (For 2016, we started work in June 2015 itself.)
- Part of the reason for the delay was because, we were busy planning the Agile Pune 2014 Conference. Now planning 2 fairly large, international conferences on the same topic, 4 months apart, can lead to them competing with each other. Each year we do organise a bunch of smaller, regional conferences. However with the Pune conference we got bit ambitious. A good lesson learned.
- The themes selected for the 2015 conference was a repeat from the most popular themes from 2014 conference. In hindsight, that was a bad idea. Participants and Companies want something new every year. (For 2016, we have 5 brand new, relevant and trendy themes: Research Camp, Lean Startup, Enterprise Agile, Continuous Delivery & DevOps and Agile in the Trenches.)
I can go on…but you get the idea.
This does not mean we will stop experimenting. We’ve been successfully running this conference for 11 years and every year we try something new, something different. That’s what keeps the excitement & enthusiasm for us (a group of volunteers, with regular day-time jobs.)
August 1st, 2015
In software world we call this speculative generality or YAGNI or over engineering.
IMHO we should not be afraid to throw parts of your system out every 6-8 months and rebuild it. Speed and Simplicity trumps everything! Also in 6-8 months, new technology, your improved experience, better clarity, etc. will help you design a better solution than what you can design today.
Just to be clear, I’m not suggesting that we do a sloppy job and rewrite the system because of sloppiness. I’m recommending, let’s solve today’s problem in the simplest, cleanest and most effective/efficient way. Let’s not pretend to know the future and build things based on that, because none of us know what the future looks like. Best we can do is guess the future, and we humans are not very good at it.
July 29th, 2015
Agile India volunteers have started working on Agile India 2016 Conference. We are planning to host the conference at the same venue (Hotel Chancery Pavilion) in Bangalore from 14th – 21st Mar 2016 (8 Days.)
We are now open for proposals to following conference themes (and here are their theme chairs):
- Research Camp (March 15th) – Jyothi Rangaiah and Ashay Saxena
- Lean Startup (March 16th) – Nitin and Tathagat (ad interim)
- Enterprise Agile (March 17th) – Evan Leybourn and Ravi Kumar
- DevOps and Continuous Delivery (March 18th) – Joel Tosi and S Sivaguru
- Agile in the Trenches (March 19th) – Ellen Grove and Leena S N
More details: http://2016.agileindia.org/#program/theme
The conference will host 3 parallel tracks. The CFP Early Bird Submissions will close on Sep 10th.
Please submit your proposals at http://confengine.com/agile-india-2016/proposals
Speaker Compensation: http://2016.agileindia.org/#speaker/compensation
Please speard the word:
Twitter: #AgileIndia2016 or @agileindia
July 6th, 2015
The jQuery foundation is making their first trip to Bangalore to bring together experts from across the field of front-end development to bring you up-to speed on the latest open web technologies. Get the inside scoop on front-end development, code architecture and organization, design and implementation practices, tooling and workflow improvements, and emerging browser technologies.
We hope that you can use this opportunity to share ideas, socialize, and work together on advancing the present and future success of the front-end eco-system.
More details: http://jqueryconf.in
First 25 people to register at http://booking.agilefaqs.com/jquery-conf-2015 can avail a special 15% discount. Use discount code – Managed@Chao$
- Dave Methvin – jQuery Core Lead | President of jQuery Board
- Kris Borchers – Executive Director of jQuery Board
- Scott González – jQuery UI Lead
- Bodil Stokke – Functional Programming Hipster
- Darcy Clarke – Co-Founder, Themify
- Eric Schoffstall – Creator, Gulp
- John K Paul – Organizer, NYC HTML5
- Alexis Abril – Committer, CanJS
- and 21 more speakers
1. Pre-Conference Workshops – Wednesday, July 22
- Optimizing and Debugging Web Sites by Dave Methvin
- Revolutionizing your CSS! by Darcy Clarke
- Contributing to the jQuery Foundation by Kris Borchers
2. Open Web Conf – Thursday, July 23
Talks on Functional Reactive Programming, ES6, Escher.jl, Famo.us, CanJS, Ionic Framework, Kendo UI, Arduino, WebRTC and The Future of Video.
3. jQuery Conf– Fri, 24th & Sat, 25th July
Talks on The jQuery Foundation, Grunt, AngularJS, TDD in JS, Securing jQuery Code, Performance beyond Page Load, Responsive Web, jQuery Gotchas, Functional Reactive Programming, RxJS, ReactJS, Om, Memory Leaks, D3 and WebRTC.
4. Hackathon hosted by Joomla project – Friday 24th 2:00 PM – Sat 25th 2:00 PM
Details will be published shortly…
Big thanks to Freshdesk for supporting this conference as a Diamond Sponsor.
Hotel Chancery Pavilion, Residency Road, Bangalore
Facebook – https://www.facebook.com/jqueryconf
Twitter – https://twitter.com/jqueryconf
LinkedIn – https://www.linkedin.com/grp/home?gid=8301395
Website – http://jqueryconf.in
June 28th, 2015
If you are using Opauth-Twitter and suddenly you find that the Twitter OAuth is failing on OS X Yosemite, then it could be because of the CA certificate issue.
In OS X Yosemite 10.10, they switched cURL’s version from 7.30.0 to 7.37.1 [curl 7.37.1 (x86_64-apple-darwin14.0) libcurl/7.37.1 SecureTransport zlib/1.2.5] and since then cURL always tries to verify the SSL certificate of the remote server.
In the previous versions, you could set curl_ssl_verifypeer to false and it would skip the verification. However from 7.37, if you set curl_ssl_verifypeer to false, it complains “SSL: CA certificate set, but certificate verification is disabled”.
Prior to version 0.60, tmhOAuth did not come bundled with the CA certificate and we used to get the following error:
SSL: can’t load CA certificate file <path>/vendor/opauth/Twitter/Vendor/tmhOAuth/cacert.pem
You can get the latest cacert.pem from here http://curl.haxx.se/ca/cacert.pem and saving it under /Vendor/tmhOAuth/cacert.pem (Latest version of tmbOAuth already has this in their repo.)
And then we need to set the $defaults (Optional parameters) curl_ssl_verifypeer to true in TwitterStrategy.php on line 48.
P.S: Turning off curl_ssl_verifypeer is actually a bad security move. It can make your server vulnerable to man-in-the-middle attack.
May 1st, 2015
Agile India 2016 Conf is Asia’s Largest & Premier Conference on Agile, Lean, Scrum, eXtreme Programming, Lean-Startup, Kanban, Continuous Delivery, DevOps, Patterns and more…
This time we are hosting a mega eight-day conference, starting on March 14th (Monday), where experts and practitioners from around the world will share their experience. The number of parallel tracks will be decided based on the quality of proposals we get. We are hoping that conference will host at least 3 parallel tracks.
Overall Agenda (tentative):
- Pre-Conference Workshop – 14th and 15th March (10:00 AM – 6:00 PM)
- Research Camp – 15th March (10:00 AM – 5:00 PM)
** Research Paper Presentation
** Open Space
** Brainstorming on improving Industry-Academia Collaboration
- Executive Leadership Conclave – 15th March (5:00 PM – 10:00 PM)
*** Keynote – 60 mins
*** Fishbowl – 90 mins
*** Group Activity on Future Direction – 90 mins
*** Cocktail Dinner Party
- Lean Startup – 16th March (9:00 AM – 6:30 PM)
*** Customer Development (Product Discovery)
*** Crafting MVPs & Safe-Fail Experimentation
*** Design Thinking
*** Lean UX
*** Lean Delivery
*** Actionable Metrics
*** 90 mins Hands-On Workshops
- Enterprise Agile – 17th March (9:00 AM – 6:30 PM)
*** Scaling Agile – Frameworks
*** People (career) & Performance Appraisals
*** Tools – Portfolio Management, Distributed Teams
*** 90 mins Hands-On Workshops
- Continuous Delivery & DevOps – 18th March (9:00 AM – 6:30 PM)
** Culture Transformation
** Software Craftsmanship
*** TDD/BDD, CI, Refactoring
*** Evolutionary Design
*** Test Pyramid
*** Legacy Code
** Cross-functional Team Collaboration
** DevOps Tools – Build, Deployment, Monitoring
** 90 mins Hands-On Workshops
- Agile in the Trenches – 19th March (9:00 AM – 6:30 PM)
*** Agile Challenges (20 mins experience reports only)
*** Abuse of Agile (20 mins experience reports only)
*** Agile Hacks – How did you tweak std. agile practices to work in your context (20 mins experience reports only)
*** Agile Tools Ecosystem
**** Visibility Tools – Project Management, Information Radiators
**** Feedback Tools – Code Quality, CI, Deployment, A/B Testing
*** 90 mins Hands-On Workshops
- Post-Conference Workshop – 20th and 21st March (10:00 AM – 6:00 PM)
We need your help to pull this off.
Roles, Responsibilities and Compensation for Program Committee Members: http://bit.ly/ai2016-program-team
–> Over the next 10 months, you would be expected to dedicate 30 mins every day (including weekends) to fulfil your role. Only if you are sure you can commit to it, please apply.
DUE DATE: May 15th.
Apply here: http://bit.ly/agileindia16-cfpc
April 11th, 2015
I’m surprised when people think Agile is perfect and if there are any shortcomings, its not the problem with Agile, instead, it is the person/team/org’s understanding or implementation issue. Some where along the way, the aspect that “We are uncovering better ways of developing software” was lost and agile became this static, rule-based prescriptive and dogmatic cargo-cult thing.
IMHO Agile has made a significant difference (some of it a a placebo effect as well) to the software industry however it has some serious limitations when you try to apply in beyond simple CRUD based applications:
- Agile works well in linear or organised complexity domains where the problem is fairly well understood (static) and we need to find/evolve the solution iteratively and incrementally. But in domains, where:
- the problem itself is unknown or constantly shifting,
- the problem has a dozen or so variables that interact non-linearly. For ex:
- in life sciences where we’re trying to understanding ageing/growth
- in anti-terrorism where we have to deal with a crisis situation
- when simulating chaotic systems like Indian traffic system
- trying to predict outcomes in systems with distributed intelligence
applying agile values, principles and practices is not the best approach in these cases. We often find ourselves lacking the right kind of thought process and tools to be able to manage such project.
- Event though the Agile luminaries claim that Agile treats software development as a Complex Adaptive System, they actually try to apply techniques that work in a Complicated Domain.
- For example, given a problem, we analyse the problem, figure our a best-bet solution (set of practices), apply the solution, see what happens, do a retrospective and tweak the solution (inspect and adapt). This is how you work in a complicated domain. In a complex adaptive domain, we try a few independent safe-fail experiments to solve the problem, but most importantly we do all those experiments in parallel (set-based development approach), so we can really amplify good patterns and dampen bad patterns. We manage the emergence of beneficial patterns with attractors within boundaries. Its like running 5 parallel A/B tests and then coming up with a solution.
- Agile folks seems to claim that distributed development is hard and you should always prefer collocation. But what about thousands of successful open source projects built by people who’ve never met each other? We seem to be missing something here. Open source project model seems to be way better at motivating people by giving them autonomy, master and sense of purpose. Most agile projects are not able to match this.
- Today velocity and bunch of other vanity metric is killing agility. There seems to be so much focus on output and very little focus on outcome and learning. Agile has very little to offer in the space of customer development, business model validation, User experience and other important aspects required for a successful product launch. Which is what Lean-Startup movement is trying to address. This is clearly a limitation of Agile methods.
What’s your take?
January 26th, 2015
TL;DR: Definition of Done (DoD) is a checklist-driven project management practice which drives compliance and contract negotiation rather than collaboration and ownership. Its very easy for teams to go down rat-holes and start to gold-plate crap in the name of DoD. It encourages a downstream, service’s thinking mindset rather than a product engineering mindset (very output centric, rather than outcome/impact focused.) Also smells of lack of maturity and trust on the team. Bottom line: Its a wrong tool in the wrong people’s hand.
The Scrum Guide™ describes DoD as a tool for bringing transparency to the work a Scrum Team is performing. It is related more to the quality of a product, rather than its functionality. The DoD is usually a clear and concise list of requirements that a software Increment must adhere to for the team to call it complete.
They recommend that having a clear DoD helps Scrum Teams to:
- Work together more collaboratively, increases transparency, and ultimately results in the development of consistently higher quality software.
- Clarifies the responsibilities of story authors and implementors.
- Enables the Development Team to know how much work to select for a given Sprint.
- Encourages people to be clear about the scope of work.
- Enable transparency within the Scrum Team and helps to baseline progress on work items
- Helps visualize done on posters and/or electronic tools.
- Aids in tracking how many stories are done or unfinished.
- Expose work items that need attention
- Determine when an Increment is ready for release
Also according to them, DoD is not changed during a Sprint, but should change periodically between Sprints to reflect improvements the Development Team has made in its processes and capabilities to deliver software.
According to the LeSS website– DoD is an agreed list of criteria that the software will meet for each Product Backlog Item. Achieving this level of completeness requires the Team to perform a list of tasks. When all tasks are completed, the item is done. Don’t confuse DoD with acceptance criteria, which are specific conditions an individual item has to fulfil to be accepted. DoD applies uniformly to all Product Backlog items.
If you search online, you’ll find sample DoD for user stories more or less like this:
- Short Spec created
- Implemented/Unit Tests created
- Acceptance Tests created
- Code completed
- Unit tests run
- Code peer-reviewed or paired
- Code checked in
- Documentation updated
- 100% Acceptance tests passed
- Product Owner demo passed
- Known bugs fixed
- Upgrade verified while keeping all user data intact.
- Potentially releasable build available for download
- Summary of changes updated to include newly implemented features
- Inactive/unimplemented features hidden or greyed out (not executable)
- Unit tests written and green
- Source code committed on server
- Jenkins built version and all tests green
- Code review completed (or pair-programmed)
- How to Demo verified before presentation to Product Owner
- Ok from Product Owner
Do you see the problem with DoD? If not, read on:
- Checklist Driven: It feels like a hangover from checklist driven project management practices. It treats team members as dumb, checklist bots. Rather than treating them as smart individuals, who can work collaboratively to achieve a common goal.
- Compliance OVER Ownership: It drives compliance rather than ownership and entrepreneurship (making smart, informed, contextual decisions.)
- Wrong Focus: If you keep it simple, it sounds too basic or even lame to be written down. If you really focus on it, it feels very heavy handed and soaked in progress-talk. It seems like the problem DoD is trying to solve is lack of maturity and/or trust within a team. And if that’s your problem, then DoD is the wrong focus. For example, certain teams are not able to take end-to-end ownership of a feature. So instead of putting check-points (in the name of DoD) at each team’s level and being happy about some work being accomplished by each team, we should break down the barriers and enable the team to take end-to-end responsibility.
- Contract Negotiation OVER Collaboration: We believe in collaboration over contract negotiation. However DoD feels more like a contract. Teams waste a lot of time arguing on what is a good DoD. You’ll often find teams gold plating crap and then debating with the PO about why the story should be accepted. (Thanks to Alistar Cockburn for highlighting this point.)
- Output Centric: DoD is very output centric thought process, instead of focusing on the end-to-end value delivery (outcome/impact of what the team is working on.) It creates an illusion of “good progress”, while you could be driving off a cliff. It mismanages risks by delaying real validation from end users. We seem to focus more on Software creators (product owners, developers, etc.) rather than software users. Emphasis is more on improving the process (e.g. increasing story throughput) rather than improving the product. Ex: It helps with tracking done work rather than discovering and validating user’s needs. DoD is more concerned about “doing” rather than “learning”. (Thanks to Joshua Kerievsky for highlighting this point.)
- Lacks Product Engineering Mindset: Encourages more of a downstream Service’s thinking rather than a product engineering mindset. Unlike in the services business, in product engineering you are never done and the cycle does not stop at promoting code to high environment (staging environment). Studying whether the feature you just deployed has a real impact on the user community is more important than checking off a task from your sprint backlog.
What should we do instead?
Just get rid of DoD. Get the teams to collaborate with the Product Management team (and user community, if possible) to really understand the real needs and what is the least the team needs to do to solve the problem. I’ve coached several teams this way and we’ve really seen the team come up with creative ways to meet user’s need and take the ownership of end-to-end value delivery instead of gold-plating crap.