The Codex of Business Writing Software for Real-World Solutions 2.pptx
7. Continous deilvery of quality product in big organizations with distributed teams, AtTask - Anahit Asatryan
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. 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. 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. 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. 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. 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
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
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. 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. Story development - branching
Separate branch per US
Team A
Team B
Team C
Master
Branch
US signed off!
Branch
Branch
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
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