Software the Agile Way....

- Lack of change management or understanding of it  -   Agile solution- Sprint review meeting ensures this - Stakeholder's understanding of the scope and scope creep   - Agile solution- Can be resolved by maintaining a well maintained Product backlog by the PO - Over-commitment  -  - Agile solution- This can be ensured using Team collaboration in Sprint planning in Scrum - Managing up instead of down or across the waves  -  - Agile solution- Collaboration resolves this - Allowing outside forces and management to affect your team   - Agile solution-Scrum Master protects the team - Not understanding your personnel resource strengths  -  - Agile solution- Retrospective meeting resolves this ( let the team resolve this) - not updating the schedule and taking action.-   - Agile solution- Shorter Sprint goal is set  -   Not communicating in the proper format at the proper level of the organization to affect a positive project outcome. -  - Agile solution-Demo meeting resolves

 Code builds without warnings (technical task)  Code review by peer as per the standard  Code unit tested (technical task)  Unit test case review as per standard  Test cases are executed (test task)  Test cases are reviewed by peer as per user story  Documentation updated (user story)  Documentation reviewed as per user story  Build pushed to demo server (user story)  

Usability - e.g Number of Clicks User Experience - e.g. Scroll acceleration Performance - e.g. latency and Throughput Sizing  - e.g. Period of Transactions to keep Scalability -  e.g. multithreading/multiprocessing Availability  - e.g 3-9s/4-9s/5-9s Security - e.g. authentication/authorization  Certificates/Legal etc