# data[].attributes.headline
Client requested more points in one iteration

# data[].attributes.subject
Client requested more points in one iteration

# data[].attributes.body
Improved from sprint to sprint. Team acted on them

# data[].attributes.body
* Clear Business Requirements
* Architecure
* Self-orgaining team

# data[].attributes.headline
Delivered more than MVP in one less iteration under budget

# data[].attributes.subject
Delivered more than MVP in one less iteration under budget

# data[].attributes.headline
Time zone difference is a benefit for this project

# data[].attributes.subject
Time zone difference is a benefit for this project

# data[].attributes.body
We helped each other out to meet the delivery of our committed user stories.

# data[].attributes.body
jBehave custom DSL framework introduced false positives. At two instances, the tests were passing because the step was incorrrectly implemented.

Good: Spot checks helped to prevent this
Look at testing approach and fill QA resource with right skill set

# data[].attributes.body
Dev resources were required to create the jBehave DSL steps to comply to the business terminology

# data[].attributes.body
Not many blockers or impediments during the project

# data[].attributes.body
It took a few iterations before we got comfortable with necessary code baseline, manual merges etc. to falicitate the code review process.

# data[].attributes.body
Brainstorming different approaches, adjusted approachjed and finally everything worked out

# data[].attributes.body
Smooth delivery overall. The team picked up user stories based on the PO's prioritized MVP user stories.

# data[].attributes.body
The team had a good initial kowledge of VSP's Product domain.

# data[].attributes.body
Because VSP were an integral part of the Development Team, no technical knowledge transfer was required at the end of the project

# data[].attributes.body
VSP appreciated the though put in to improve the user's UI experience

# data[].attributes.body
Less was more for her. Even though the project was smooth. Building relationship was difficult

# data[].attributes.body
Identified bugs which where not get surfaced using jBehave

# data[].attributes.body
Transparent communication.

# data[].attributes.body
There were some challenges with pull requests at the beginning.

# data[].attributes.body
Stable dedicated resources.

# data[].attributes.body
The stories were neatly organized so that it mad it easy to add the following ones.

# data[].attributes.body
Git pull request via Stash allowed multiple reviewers to provide their respective coide review comments

# data[].attributes.headline
No lost time due to missing groomed backlog stories

# data[].attributes.subject
No lost time due to missing groomed backlog stories

# data[].attributes.body
Decision to create a jBehave steps tailored to our business domain provided VSP to provide their business sign-off.

# data[].attributes.body
Deskchecks
Partial deskcheck were conducted in a timely manner to de-risk potential re-work. Ie. UI was presented based on mocked data,
then later, the JBehave tests were reviewed and the UI was re-deskchecked ONLY if deemed necessary.

# data[].attributes.body
Good aquiantace of domain knowledge facilitated story readiness

# data[].attributes.body
The user stories met the definition of readyness. Acceptance scenarios were clearly defined along with the respective test data.

# data[].attributes.body
The systems on which the solution depended on were stable APIs (ClientProduct, etc).

# data[].attributes.body
It was very helpful to have dev on theirs side.

# data[].attributes.body
Proven within the first iteration. Amazing. ****

# data[].attributes.body
First two
sprints required a lot of refactoring on UI side.

# data[].attributes.body
Completed the project deliverable within the plannned number of iterations.

# data[].attributes.headline
Handled difficult client resource smoothly

# data[].attributes.subject
Handled difficult client resource smoothly

# data[].attributes.body
Team did a great job working with the client resource with PM intervention

# data[].attributes.body
Involving VSP client resources in the project;
Part of the problem & solution. Brings better synergy

# data[].attributes.headline
Sales: Start dates are always a moving target

# data[].attributes.subject
Sales: Start dates are always a moving target

# data[].attributes.body
It impacts VSP as well to ensure we have secured right resources for the project. This project team selection was great. All senior team members, self-organizing.
Time to bring new blood into VSP for team professional growth

# data[].attributes.headline
Sales: Little bit more back & forth with client

# data[].attributes.subject
Sales: Little bit more back & forth with client

# data[].attributes.body
Requirements are detailed and fully vetted

# data[].attributes.body
Earlier exposure to the project's domain knowledge was very beneficial to the team's quick ramp-up in the requirements for a projects were two other vendors had failed previously.