Fiserv Auckland - Intermediate Software Test Engineer: Difference between revisions

Jump to navigation Jump to search
m
Line 82: Line 82:
==Agile at Fiserv ==
==Agile at Fiserv ==


Fiserv used the [https://www.scaledagileframework.com '''Scaled Agile Framework''' (SAFe)] to govern their Agile practices. Squads, with typically ten members, engaged in common Agile Rituals, and was responsible for SDLC through to integration. We followed Gitflow (on TFS).  
Fiserv used the [https://www.scaledagileframework.com '''Scaled Agile Framework''' (SAFe)] to govern their Agile practices. Squads, were typically about ten in size, and engaged in common Agile Rituals, and were responsible for SDLC through to integration. We followed Gitflow (on TFS).  


The squad
The squad
* Engaged in Agile Rituals: Daily stand-ups, backlog grooming, estimation, planning, demos, and retros.
* Engaged in Agile Rituals - stand-ups, backlog grooming, estimation, planning, demos, and retros.
* Owned the development lifecycle: story design, implementation, testing, and integration
* Owned the development lifecycle - story design, implementation, testing, and integration
* Followed Gitflow, using feature branches for development and integrating changes into release-train branches.
* Followed Gitflow - feature branches for development and integrating changes into release-train branches.
* Contributed to quality checking at various stages before deploying code changes to production.
* Contributed to quality checking at various stages before code changes were deployed to production.

Navigation menu