Scrum, for example, doesn't specify technical practices. It's rumored that it did initially, to make the framework more effective, but Ken and Jeff pulled them before formally announcing it.
As a result around 10% of Scrum teams, according to VersionOne's 11th Annual State of Agile Report, incorporate some or all of the technical practices from Extreme Programming (XP).
- Title Page
- Copyright and Credits
- Packt Upsell
- Contributors
- Preface
- The Software Industry and the Agile Manifesto
- Why the software industry needed to change
- Incremental – adaptive versus waterfall – predictive
- Agile is a mindset
- Summary
- Agile Software Delivery Methods and How They Fit the Manifesto
- Introducing Scrum to your Software Team
- Gathering Agile User Requirements
- Bootstrap Teams with Liftoffs
- Metrics that will Help your Software Team Deliver
- Software Technical Practices are the Foundation of Incremental Software Delivery
- Tightening Feedback Loops in the Software Development Life Cycle
- Seeking Value – How to Deliver Better Software Sooner
- Using Product Roadmaps to Guide Software Delivery
- Improving Our Team Dynamics to Increase Our Agility
- How to create high-performing teams
- The stages of team formation
- Stage 1 – forming
- Stage 2 – storming
- Stage 3 – norming
- Stage 4 – performing
- Stage 5 – adjourning/mourning
- Learning by practicing
- Summary
- Baking Quality into Our Software Delivery
- The Ultimate Software Team Member
- Moving Beyond Isolated Agile Teams
- How an Agile approach will organically flatten an organizational structure
- Self-selection to create a true-self organization
- Modern leadership
- The art of Agile leadership
- Organizational styles for flatter structures
- Summary
- Other Books You May Enjoy
Not all frameworks prescribe technical practices
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.