BamBam! Teamwork Academy: Agile


Published on

BamBam! Teamwork Academy is a new series by 84kids focusing on online collaboration, project management and Agile approach to software development.

Each presentation contains a number of useful tips that can be applied in practice to all kinds of development business, from small software houses to engineering companies running on workflows to large production ventures.

Feel free to comment and share!

Published in: Business

BamBam! Teamwork Academy: Agile

  1. 1. # Agile
  2. 2. What is Agile? Agile is a group of software development methods based on iteration and increment. The main difference from traditional approach to development is that Agile promotes dynamic evolution of software through development cycles (iterations) and allows for rapid change to the product in response to customer demand. # Agile
  3. 3.  What is more important for you: individuals and interactions or processes and tools?  Do you spend more time making your product usable or making documentation how to use it?  Would you rather collaborate with your clients or negotiate hard?  Are you able to respond to changes on-the-fly or do you stick to the plan no matter what? Will Agile work for my company? # Agile
  4. 4. If you chose at least one answer in bold then Agile is definitely worth giving a shot # Agile
  5. 5.  Feature Driven Development  Dynamic Systems Development Method  Test-driven Development  Extreme Programming (XP)  Scrum  Lean Software Development  Kanban Selected methods of Agile # Agile
  6. 6.  Agile will not solve your problems off the cuff  The process of adopting agile can be painful. Make sure that your team is well informed about the changes it involves  Adopting agile is about changing mindset, not tools What should I know before adopting Agile? # Agile
  7. 7.  Poor or lack of communication  Badly constructed teams (no complementation)  No customer participation  Poor planning  Not enough determination in fighting resistance from the team accustomed to old working habits Common mistakes of new Agile teams # Agile
  8. 8.  Use abstract estimation points (like colors or shapes) to represent the size of new work  Don’t use deadlines until you and your team know how quickly a task can be completed  Engage your team in planning iterations and respect the value of their insights  Give your team a prioritized list of requests (backlog) rather than a set of directives  Always foster an environment of trust in your company How to make your team commissioned # Agile
  9. 9. Yes, let’s do this! Ready to apply Agile in practice?