We were painfully surprised when the firmware team, out of nowhere, showed the software that our team had planned to build, at our halfway mark. We lost the project to them. We worked in a waterfall manner. They were agile.
There is probably no more ubiquitously abused professional growth tool than the one-on-one meeting between an employee and his or her manager.
If we want our teams to be successful, we need to start our conversation with what we believe to be the most important principles to pay attention to in software projects and use those principles as our true North.
Want to see GitHub's Oval Office replica? Complete with Octocat Seal? Check that out along with the Stack Exchange homegrown DevOps tools, the CSS Animation Cheat Sheet, and another DZone "dev" shirt sighting!
I do not believe that it is possible to sell Agile to a company, they must come to the realization of what it entails themselves.
Doing a stand-up meeting (a.k.a daily scrum) meeting should be simple, so why are so many teams doing it wrong?
The goal is not to write code faster. The goal is to produce valuable, working, testing, remediated code faster.
As developers enter the work force, they quickly begin to realize that being paid to do a job is different than programming as a hobby. The following is a series of realizations (in no particular order) about working for a business and developing:
Being able to release faster, is not just about pushing code to production. I will cover how we got to the point where we could release Mule faster.
I have observed that the most unproductive day would be to have scattered meetings all throughout the day.
However you build your software system, creating a well-structured architecture isn't something that happens all by itself. You need to put time, effort and discipline into it.
On the application side, there are several singleton processes - for example cron configurations - that are usually run only once on the whole data set. For a certain category of singleton processes we can switch to a shard-like architecture that can scale first to multiple processes and when necessary to multiple servers.
This week we bring you a Dev of the Week with a twist: We're talking to Scott Westfall, our new Director of Engineering here at DZone.
Our organizations are crippled by separation. To be effective, we must repair these broken relationships within teams and within whole organizations.
I was asked recently to review The Professional Scrum Masters Handbook. As I read this book there were times that I shouted at it and I almost stopped reading in disgust around chapter four.