Fiserv Auckland - Intermediate Software Test Engineer: Difference between revisions

Jump to navigation Jump to search
m
Line 79: Line 79:


==Agile at Fiserv ==
==Agile at Fiserv ==
:Fiserv uses the [https://www.scaledagileframework.com Scaled Agile Framework] which is ...  
 
:* XXX to be updated XXX The squads were usually  2 Dev's, 1 tester, ½ BA, with access to design. In addition, the PO providing direction but considered just outside the squad.  
We used the [https://www.scaledagileframework.com '''Scaled Agile Framework''' (SAFe)] to govern our 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).  
:* XXX to be updated XXX Most squads are product facing, but there are also a number of squads that provide internal technical and support services to help the product squads. (DB, Platform, API, Automation, Code Health etc) Squads are trusted to ask for assistance when needed, and when to reach out to others when there are shared or over lapping responsibilities.
 
The squad
* Engaged in Agile Rituals: Daily stand-ups, backlog grooming, estimation, planning, demos, and retros.
* Owned the development lifecycle: story design, implementation, testing, and integration
* Followed Gitflow, using feature branches for development and integrating changes into release-train branches.
* Contributed to quality checking at various stages before deploying code changes to production.


==Tools I used at Fiserv==
==Tools I used at Fiserv==

Navigation menu