SCRUM vs Traditional Project Management
| SCRUM | Traditional Project Management | |
| Emphasis | In persons | In processes |
| Documentation | Minimum | Excesive |
| Process Style | Iterative | Lineal |
| Ahead Planning | Low | High |
| Requirements Prioritization | Based on business value and constantly updated. | Fixed in the project plan. |
| Quality Guarantee | Client centralized. | Processes centralized. |
| Organization | Auto-organized. | Managed. |
| Management Style |
Decentralized. | Autocratic. |
| Changes | Backlog updates and prioritization. | Formal change management. |
| Leadership | Collaborative, services leadership. | Command and control. |
| Performance measurement | Business value. | Based on plan. |
| ROI | Early / across the project. | At the end of life of the project. |
| Participation of the change | High across the project. | Varies depending of the life cycle of the project. |
Jafet Sánchez
Software Engineer
Software Engineer with +20 years of experience. Specialist in getting s**t done. Web Developer currently focus in the e-Commerce world with SAP Hybris and Magento (and soon Salesforce).
Happy Husband and Father of two, Jujitsu practicioner, Carnivorous, Catholic and currently living in this beautiful and cold place called Chicago
I LOVE MY LIFE 🙂