Software the Agile Way....

Waste is simply anything that does not add real value to the overall end goal is considered waste. Things that could be considered waste are  - Unnecessary features or functionality  - Over engineering  - Unnecessary code  - Weak requirements  - Bureaucracy  - Anything that slows down or delays the team  - Weak testing, resulting in many production issues  - Poor or unnecessary communication  - Unnecessary documentation (note documentation may still be needed)  - Anything that wastes time without any valuable benefit   "The Seven Wastes of Software Development":  1. Partially Done Work  2. Extra Features  3. Relearning  4. Handoffs  5. Delays  6. Task Switching  7. Defects

http://agileramblings.com/2012/12/11/littles-law-its-not-about-the-numbers/

List of Topics on which I specialize and would like to talk in my future posts..... Agile Modelling Agile Unified Process (AUP) Crystal Clear / Methods Dynamic Systems Development Method (DSDM) Extreme Programming (XP) Feature Driven Development (FDD) Graphical System Design (GSD) Kanban Lean Software Development Scrum Velocity Tracking Software Development Rhythms

  Improve quality    -     Reduce cost      Improve time to market      Improve teamwork      Increase customer involvement  

1-Focus on Solutions not Problem Project management is a tough role. You often find yourself being pulled between keeping users, subordinates, team members and senior people happy. Given these demands, what do the best project managers do that makes them stand out from the crowd? 1. Focus on Solutions not Problem Problem solving and breaking through constraints is an essential part of managing projects. Those that excel as project managers have a mindset where they focus on finding solutions to problems. They keep asking themselves how they can overcome whatever barriers arise. 2. Participative and decisive All the best project managers understand the need to communicate and consult. They also know that lots of talking and procrastination achieves nothing. Finding the right balance between consulting, deciding and acting is what separates the best from the rest. 3. Focus on customer In every project there are customers. They might be internal or external or a combinati...

Practice #1: Version control system Practice #2: Continuous integration Practice #3: Automated testing Practice #4: Refactoring Practice #5: Simple design Practice #6: Collective code ownership reference -  http://www.citerus.se/post/1165683-the-top-six-technical-practices-every

http://www.scrumexpert.com/tools/using-commercial-scrum-tools-for-free/?goback=%2Egde_81065_member_215182497

Pareto's Principle  - The  80-20 Rule -  How the 80/20 Rule Helps Us be More Effective Decision making with AHP (Analytical Hierarchical Process) MoSCoW Rule Boston Consulting Group BCG Matrix http://www.valueeng.org/finance-manager-125/boston-consulting-group-bcg-matrix.html

http://chrissteeleagile.com/scrum-kanban-scrumban/