Confidential 10/7/2013 1
AGILE TOUR YEREVAN
05, October, 2013
Continuous delivery of quality
product in big organizations
...
AtTask as a company
• Established on - Head office – 2001,
Yerevan office - 2008
• Company size – 450+ employees
• Number ...
AtTask as a product
Enterprise Work Management platform
that helps to:
1. Identify work
2. Prioritize
3. Plan
4. Coordinat...
Agile in AtTask
Agile principles that are deeply applied in AtTask are:
• Customer satisfaction
• Adopting to changing req...
Adoptions from Scrum
From Scrum we have taken:
 Roles
 Sprint
 Meetings
 Daily Scrum
 Backlog Refinement (grooming)
...
Adoptions from Extreme Programming and Kanban
From Extreme Programming it has taken:
 Frequent releases
 Extensive unit ...
Scaled Agile Framework (SAFe)
http://scaledagileframework.com/
AtTask work flow overview
Strategy
Requirements
Requirements prioritization
Release content definition
Epics/USs prep. by ...
1. Define
2. Prioritize
3. Split
Release content definition
1
11
1
3
2
2
2
2
3
3
3
3
User Story preparation and Sign off
 Spec. by PM
 Design by UX designer
 Tech. Approach by Tech. Approach owner
 Test ...
Story development
 Implementation in sep. US branch
 Test map review/ layering and automation
 Tests run on Jenkins CI ...
Story development - branching
Separate branch per US
Team A
Team B
Team C
Master
Branch
US signed off!
Branch
Branch
Test map review/ layering and automation
 Helps to:
 Shorten time for test run  min Selenium tests
 Reduce server load...
Continuous deployment and test run
 Bespin CI organization
 Smart suite logic
 Slices
• General Access
• Early Access
• PitBoss
Feature Accessibility
PitBoss logic
PitBoss – check integrated into US
 Rollback without deployment
 Deployment & Release separation
PitBoss –...
Early Access logic
Early Access – mechanism for enabling
features on production before GA
Early Access
From continuous integration to
continuous delivery
continuous
integration
continuous
delivery
Achievements
Continuous control over product quality
 test maps – review/ layering/ automation
 continuous test runs- fo...
7. Continous deilvery of quality product in big organizations with distributed teams, AtTask - Anahit Asatryan
Upcoming SlideShare
Loading in …5
×

7. Continous deilvery of quality product in big organizations with distributed teams, AtTask - Anahit Asatryan

518 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
518
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

7. Continous deilvery of quality product in big organizations with distributed teams, AtTask - Anahit Asatryan

  1. 1. Confidential 10/7/2013 1 AGILE TOUR YEREVAN 05, October, 2013 Continuous delivery of quality product in big organizations with distributed teams Anahit Asatryan Senior QA Automation Engineer
  2. 2. AtTask as a company • Established on - Head office – 2001, Yerevan office - 2008 • Company size – 450+ employees • Number of dev. teams – 14 teams • Locations over the world – US, UK, Japan, China and Armenia Dev teams located in US and Armenia UK, Japan and China – only Sales
  3. 3. AtTask as a product Enterprise Work Management platform that helps to: 1. Identify work 2. Prioritize 3. Plan 4. Coordinate 5. Execute 6. Deliver 7. Measure 8. Collaborate
  4. 4. Agile in AtTask Agile principles that are deeply applied in AtTask are: • Customer satisfaction • Adopting to changing requirements & circumstances • Frequent software delivery • Progress is a working software • Sustainable development • Daily cooperation with business people • Motivated individuals • Technical excellence
  5. 5. Adoptions from Scrum From Scrum we have taken:  Roles  Sprint  Meetings  Daily Scrum  Backlog Refinement (grooming)  Sprint Planning  End of cycle  Sprint Retrospective  Artifacts  Product backlog, Sprint backlog, Increment, Burn down
  6. 6. Adoptions from Extreme Programming and Kanban From Extreme Programming it has taken:  Frequent releases  Extensive unit testing  Programming of features only when actually needed From Kanban it has taken:  Limiting work-in-progress (WIP)  Workflow visualization  Workflow monitoring, measurement and reporting
  7. 7. Scaled Agile Framework (SAFe) http://scaledagileframework.com/
  8. 8. AtTask work flow overview Strategy Requirements Requirements prioritization Release content definition Epics/USs prep. by PM Backlog grooming US is ready US development US is ready for sign off US signed off Pull request by team US is ready for release
  9. 9. 1. Define 2. Prioritize 3. Split Release content definition 1 11 1 3 2 2 2 2 3 3 3 3
  10. 10. User Story preparation and Sign off  Spec. by PM  Design by UX designer  Tech. Approach by Tech. Approach owner  Test Map by Manual QA ??? !! ?! !? !?
  11. 11. Story development  Implementation in sep. US branch  Test map review/ layering and automation  Tests run on Jenkins CI tool User story is ready for sign off !   
  12. 12. Story development - branching Separate branch per US Team A Team B Team C Master Branch US signed off! Branch Branch
  13. 13. Test map review/ layering and automation  Helps to:  Shorten time for test run  min Selenium tests  Reduce server load  Functionality coverage visibility  Fulfill gaps in future & include in regression suite Branch Test scenario 1 Test scenario 2 Test scenario 3 Test scenario 4 Test scenario 5 Test scenario 6 Test scenario 7 Test scenario 8 Test scenario 9 Unit Integration Selenium API Not for smoke Integration API Unit Integration          Bespin
  14. 14. Continuous deployment and test run  Bespin CI organization  Smart suite logic  Slices
  15. 15. • General Access • Early Access • PitBoss Feature Accessibility
  16. 16. PitBoss logic PitBoss – check integrated into US  Rollback without deployment  Deployment & Release separation PitBoss – check integrated into US  Rollback without deployment  Deployment & Release separation
  17. 17. Early Access logic Early Access – mechanism for enabling features on production before GA Early Access
  18. 18. From continuous integration to continuous delivery continuous integration continuous delivery
  19. 19. Achievements Continuous control over product quality  test maps – review/ layering/ automation  continuous test runs- for each US/issuing fixing branch during story implementation and pull request Readiness to deliver at any point in time – green Master Ability to release as soon as feature is ready - delivering USs independently Flexible and easy code quality control - branching / pitBoss    

×