InfoQ: Lean Startup: Why It Rocks Far More Than Agile Development. Nathan Herring presents the available storage options at Google, the ideal characteristics of a storage service, and the actual implementation of Google Cloud Storage.
InfoQ: Adopting Agile Development Practices: Using Patterns to Share our Experiences. Abstract The increasing popularity of Agile approaches for software development is forcing an increasing number of organizations to deal with issues of Agile adoption (and adaptation).
In this article I introduce patterns that focus on the dynamics of adoption rather than the structure that results from adoption. Essential Skills for the Agile Developer. Essential Skills for the Agile DeveloperA Guide to Better Programming and Design by Alan Shalloway, Scott L.
Bain, Ken Pugh, and Amir Kolsky. This book answers the question many developers have after taking some initial Agile/Scrum training – “OK, how do I write code now that we are building our software in iterations?” State of Agile Development Survey Results. The MindTouch Way: Agile Software Development with GitHub. Every Thursday, MindTouch delivers a new release of our software to all MindTouch customers.
MindTouch development teams work in a synchronized two week cadence, known in Agile development philosophy as a “sprint”, to complete bug fixes, performance optimizations, and features for the two Thursday releases encompassed by the sprint. In 2011, after deciding to switch our software management system from Subversion to Git, it made perfect sense for MindTouch to use the Git-powered GitHub site to house our code. GitHub has empowered MindTouch developers, testers, and release engineers to create workflows that increase confidence in the quality of code being shipped. By storing MindTouch code on GitHub, MindTouch has a powerful platform for software development collaboration. MindTouch developers can make a copy of the core codebase on their workstation and work on a specific feature or optimization without disturbing others’ work or the stability of the code in QA or production. Turbo-Charging Agile Software Development with Lean Methods.
Bio Satish Thatte has over 30 years of industry experience in large, multinational companies (Texas Instruments, Bellcore and LG Electronics), and entrepreneurial companies and start-ups.
Dr. Thatte was the founder and CEO of New Synergy Group where he offered customized training, workshops, coaching and consulting services. Agile Planning. My thoughts on Agile. The seeds that you plant at the beginning of an organization’s life influences how the organization grows over time.
I think it’s safe to say that you have some macro goals: Predictability: you as managers want to predict what will happen and when it will happen Flexibility: you want to be nimble to satisfy customers and close sales Open Communications: you guys want to have good, open, honest communications with the team, especially when the situation is suboptimal It’s been my experience that agile achieves the above goals, even though it might not seem that way.
Waterfall, lots of up-front type of methodology is not agile and will ultimately result in falling short of the above stated goals, despite that having a long-term plan seems to jibe with predictability. So, when I say ‘agile’, I mean the following: The team works towards periodic goals. All tasks are placed in a central ‘backlog’ and prioritized in that backlog. Backlog re-prioritization can happen any time. Agile in the Defense Industry. Whenever I hear other software leads complain about their “waterfall-ish” development process, I always ask why they haven’t tried something more agile.
The most common answer I’ve heard back is that they don’t know where to begin. The fact that entire books have been written on the subject of Agile software development doesn’t make it any easier. Explaining to your project management team that you want drop everything you know and try something completely different - that seemingly requires entire books to describe, can be a pretty big sell.
That type of change tends to make project management cringe. The truth is Agile software development is phenomenally simple and highly customizable. The Process. Confessions of an Agile Addict. Agile Teams, from Good to Great. Bio David Bulkin is a strong leader, technologist and process engineer with over 20 years experience in applying Lean processes to manage portfolios, projects, people, process, and technology for competitive advantage.
He has helped numerous teams apply agile project management and engineering methods as a practitioner and coach. He is a frequent speaker at user groups and blogs on the subject. VersionOne helped pioneer the agile management tool in 2002 – way before it was the cool thing to do in the software development market. Some Inconvenient Truths About Software. An essay for managers and executives who are not in the business of software, but rely on it’s in creation for their business’s success.
Software isn’t like conventional project work. It’s invisible. You can’t see it. You can’t touch it. Agile and SEMAT - Perfect Partners - ACM Queue. Ivar Jacobson, Ian Spence, and Pan-Wei Ng Today, as always, many different initiatives are under way to improve the ways in which software is developed.
The most popular and prevalent of these is the agile movement. One of the newer kids on the block is the SEMAT (Software Engineering Method and Theory) initiative. As with any new initiative, people are struggling to see how it fits into the world and relates to all the other things going on. For example, does it improve or replace their current ways of working? The good news is that both of these initiatives promote non-prescriptive value-based philosophies that encourage software development teams to select and use whatever practices best fit their context and, more importantly, continuously inspect, adapt, and improve their ways of working. The Value Proposition for Agility–A Dual Perspective.