Agile Team Building

Introduction

During  2014, in my start-up we had an agile training with Mr. Amr Elssamadesy the famous Agile trainer and the author of Agile Patterns: The Technical Cluster and Agile Adoption Patterns: A Roadmap to Organizational Success.

Mr. Elssamadesy joined the company during critical circumstances. Back then, we had new team of developers, business, and quality control and this team was considered as a "Junior"  team where as most of them were fresh grads or with 2-3 years experience in some cases. This was not the only problem, the major problem was that we had a mega huge product which was built during the previous 2 years that has a lot of very complicated features.

The major problem here is that, the very successful business team has sold this product to many clients and each client now are ready to operate and have their own very long list of requirements and customization needed. The product is really huge to the level that it is not very easily customizable. There wasn't any possible solution for the company to succeed by gaining the customer satisfaction. By very optimistic calculations, the new "Junior" team will take no less than 3 months to warm up and getting into the mode. Plus, the code base was really huge.

Successful Team Leading

NOTE: This article is written by Dave Chaplin, an IT Consultant with 10 years experience. He leads and mentors teams of developers on agile .NET projects and has extensive experience in agile development techniques, particularly Test-Driven Development. Dave can be emailed atdavechaplin@byte-vision.com. Date: Sunday, October 06, 2002 And it was taken from the following URL: http://www.byte-vision.com/TeamLeadingTipsArticle.aspx ================================================================================================== Successful Team Leading

Abstract

This article describes some practical tips for successfully leading a team of software developers. It defines what success means and then describes some very common sense tips for achieving that success.

What deems a project to be successful?

The primary goal of any software project is to meet the user requirements and make sure the users are delighted. If something has been built that nobody wants, it makes no difference what happens to staff turnovers, budgets or training. If requirements are not met, the project is a failure. The next goal after requirements is probably to complete the project within the required budget. After that, there might be others requiring staff to be trained, and so on.

Here are a number of tips for team leaders to help them achieve success in their own projects.