WINIT - Web Application Process, Testing

Web Applications -- ASP.NET ; for a couple of Desktop Apps, C# and VB.NET was used.
================================================================

Lakeplace --- booking reservations for small motels near lakes
AAXA ---- Cargo transportation & logistics
Fine Tuxedos -- online Tuxedos sale
Etc.

1. Client interactions / comms -- requirements gathering.
2. Define workflows / business logic
3. Wireframes [sketching, dreamweaver / frontpage, photoshop]
4. Style guide ---
5. Front End design -- ASP.NET, PHP, SQL (Own 3 tier architecture that dev were supposed to follow).
6. Backend Dev
7. Paypal integration
8. UI and Functional Testing
9. Client review every couple of days.

-- No formal test strategies.
-- No formal test planning either
-- Manual testing
-- Write test cases based on workflows
-- Test, raise bugs, get them closed by dev, report bugs
-- Test paypal integration

Paypal Integration Testing...

1. Get details of dummy credit card
2. Checkout button --> Paypal --> Paypal gateway processing --> Back to your website
3. Check for session expiry, session ends.
4. Check what happens if Payment Gateway stops responding.
5. Check for data going to the backend.
6. What happens upon successful transaction -- database, messages, etc.
7. Check receipts are generated and sent to customer email account

Agile Conflict Resolution

Conflict resolution

==============

Telstra

--------

W was a product owner for one of my teams in Media. I noticed that he was increasingly getting himself excused from user story refinement sessions, beginning to withdraw. This was also the time when there were interactions with the senior management in media around team restructuring (feature teams). 

One fine morning W summoned me to his 20th floor office. The moment he saw me, he turned red faced. The moment we went into a meeting room, he blasted me off. For the next 15 minutes he vented his ire. He seemed to harbour a fear that his job is on threat. And that I as an Agile Coach / Scrum Master was conniving with the senior management to throw him out. 

There was a context to this. Telstra was going thru a gigantic transformation exercise. Age old team structures were being taken down to reorganise people into meaningful cross-functional teams. 

I patiently heard W. Apologised to him if there was any misunderstanding. And now that he was at ease after letting himself out, I started putting forward the background of what was happening. 

1. What are your concerns / fear?

2. In your opinion how could we have approached this?

3. Is there a better approach you think could assuage you and other people?

4. Let's agree to a way of communication going forward. I want to be honest with you, and expect the similar honesty from you. 

It was then W came out with the fact that he was caring for a dying mum, and his emotions were getting mixed with the uncertainty times in the office.

After the matter was resolved, an hour later I receive an email where W officially apologised for his behaviour.

Common Agile Metrics

• Lead Time
• Cycle Time
• Sprint Burndown - tells us how much value has been delivered.
• Sprint Velocity
• No. of deployments to prod
• Average time to prod.

DoR and DoD in TxS...

DOR in TxS
==========

1. User stories written in As a < type of user >, I want < some goal > so that < some reason >.
2. Acceptance Criteria written, and in BDD format - Given, When, Then.
3. User stories approved by PO.
4. User stories prioritised by PO.

DoD in TxS
==========

1. Development is complete.
2. Pega unit is complete
3. Code reviewed.
4. Relevant comments and attachments made.
5. Dev QA complete
6. ZSIT / IT complete
7. System Testing complete
8. UAT complete (based on TC provided by business).
9. No open Sev 1/ Sev 2 bugs.
10. US approved by PO.