Agile toolkit

1,791 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,791
On SlideShare
0
From Embeds
0
Number of Embeds
636
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Increases productivity, as the team shares best practices for development and deployment, and developers need focus only on current business requirementsImproves quality, so the final application meets the needs and expectations of usersBreaks boundaries through collaboration and smooth information flowAccelerates development through simplified integration[2]Cuts maintenance time by synchronizing application and designMaximizes investments in skills, processes, and technologiesIncreases flexibility by reducing the time it takes to build and adapt applications that support new business initiatives
  • Capture requirementsManage backlogTrack iteration progress
  • Prefer tools with open APIs, plug-ins, web services, query language etc.
  • Explain on how to create simple backlog using excel/evernote etc.
  • We’ve started with sticky notes
  • Pros:High visibilityEasy to use and maintainCons:Statistics are not automatically createdNeed to go into the room
  • Pros:Can access from anywhereCan be sent in emailCons:Only one editor at a timeNeed to add statisticsNot automatic
  • Make it easy for the developers to write and test code
  • We’ve started with sticky notes
  • Agile toolkit

    1. 1. The agile toolkit<br />Dror Helper<br />http://blog.drorhelper.com<br />
    2. 2. Don’t forget<br />Individuals and interactions over processes and tools – the agile manifesto<br />
    3. 3. What is ALM?<br />“Application Lifecycle Management (ALM) is a continuous process of managing the life of an application through governance, development and maintenance.”<br />Wikipedia<br />http://en.wikipedia.org/wiki/Application_lifecycle_management<br />
    4. 4. Application life cycle<br />
    5. 5. The team<br />
    6. 6. Product Owner<br />What am I getting next release?<br />Will you be able to finish on time?<br />What won’t we be in the release?<br />
    7. 7. Developer<br />What do I do next?<br />How well are we doing?<br />Help me write code – faster!<br />
    8. 8. Tester<br />What new features are ready to test?<br />What are the changes from last release?<br />Keep and track bugs<br />What are the known issues<br />
    9. 9. Operations<br />Deploy to test environment<br />Deploy to clients/production<br />Configuration management<br />
    10. 10. Support<br />What are the known limitations?<br />How to solve this problem (FAQ)<br />How do I notify development of a new issue?<br />
    11. 11. Choosing the right tool(s)<br />6 tips to help you design ALM strategy<br />
    12. 12. Communication<br />Facilitate high bandwidth communication<br />Beware of person-tool communication!<br />Individuals and interactions over processes and toolsthe agile manifesto<br />
    13. 13. Agile inside!<br />Tools must support common agile practices:<br />User stories, Iterations, acceptance testing, continuous integration, refactoring, Unit testing.<br />
    14. 14. Let the team decide<br />One those who use the tool pick the tool<br />Better – the team select, build and maintain the agile ALM infrastructure<br />
    15. 15. Tools should be adaptable<br />The ALM tools should be extensible, customizable and adaptable so they can grow together with the project (and team)<br />
    16. 16. Single vs. Multi Vendor Approach<br />Integrated solution vs. best of breed<br />
    17. 17. Don’t be afraid to change<br />Because that’s what being agile is all about!<br />If it’s not working – find something else.<br />
    18. 18. The tools<br />
    19. 19. ALM<br />Backlog<br />Track iteration progress<br />Development tools<br />Issue tracker<br />Continuous integration server<br />Deployment<br />
    20. 20. The backlog<br />Product’s master list<br />Record requirements<br />
    21. 21. Tracking iteration<br />The “Task board”<br />Track to-do, in progress and done tasks<br />Provide statistics<br />
    22. 22. Case study<br />From sticky notes to TFS<br />
    23. 23. Post-it + wall<br />
    24. 24. Excel in shared folder<br />
    25. 25. TFS + Work item manager<br />
    26. 26. Development tools<br />
    27. 27. Continuous Integration<br />Build Server<br />What’s new?<br />Commit<br />There you go<br />Start working<br />Build artifacts<br />We automatically got<br /><ul><li>Error reports & logs
    28. 28. New version installer
    29. 29. Help files
    30. 30. More…</li></ul>Source Control<br />Build Agents<br />
    31. 31. CI server - TeamCity<br />
    32. 32. Issue tracking<br />The bridge between the departments<br />Product owner<br />Development team<br />Testers<br />Support<br />
    33. 33. Case study<br />From in house to cloud<br />
    34. 34. Other Agile ALM tools<br />Telerik’s team pulse http://www.telerik.com/agile-project-management-tools.aspx<br />TargetProcesshttp://www.targetprocess.com/<br />
    35. 35. Summery<br />Individuals and interactions over processes and tools – the agile manifesto<br />There are many tools out there – experiment<br />Don’t be afraid to update and change tools<br />

    ×