We forecasted we could get 5 story points done during this sprint. Our forecast is on conservative side primarily based on team member skill mix and technical demands of the actual prioritized PBIs. As this is the first sprint for the Brain Cradle Team, we were not sure what our actual velocity would be. Regardless, the forecast accounted for the fact that we each would need to locally configure the project, work through the learning curve of new frameworks, and be able to iterate on our localhost before we were able to begin work on the stories that actually delivered product value. The forecast correlated to the first story from our Initial Ordered Product Backlog:
| Number | Title | Story Points | Summary |
|---|---|---|---|
| 1. | Site Navigation | 5 pts | Andrew Kiriakedes (Andy) would like to be able to click on links at the top of the website that are consistent across pages, clearly outline where each link will send him, and ensures that he's only ever one click away from each of the sites primary features. |
We had few hiccups, but were able to close on the selected user story forecasted within the sprint (reference our Definition of Done).
We deployed the user story in production at following URL:
(reference our Sprint Task & Acceptance Criteria).
Our burndown chart, shown below, is based on the completion of each user story Refer to User Story in Trello which were decomposed from the PBIs committed to the sprint.
What did you accomplish yesterday?
setup local environment
What will you do today?
download the shell code and dev framework
What obstacles are impeding your progress?
none
What did you accomplish yesterday?
I created a basic code framework and local environment along with instructions for the team to replicate on their local.
What will you do today?
Explore firebase hosting
What obstacles are impeding your progress?
none
What did you accomplish yesterday?
Setup local environment
What will you do today?
Research BDD with angular
What obstacles are impeding your progress?
No past experience on angular framework.
What did you accomplish yesterday?
downloaded the basic shell and worked on front end css
What will you do today?
expand on the front end code to build basic navigation
What obstacles are impeding your progress?
none
What did you accomplish yesterday?
I deployed the shell app on firebase hosting server.
What will you do today?
Working on unit test cases for the app
What obstacles are impeding your progress?
Limited knowledge on Unit Test integration with angular
What did you accomplish yesterday?
Identified and integrated BDD framework with angular using selenium
What will you do today?
Create BDD test suite
What obstacles are impeding your progress?
No past experience on angular framework. Help in form of reference articles are being provided.
IRP = Impediment Removal Plan
Not sure how to setup development framework?
IRP: Shivas provided instructions on slack to download base development framework and setup on WebStorm.
Where do I put the img/video folders in Angular? Do the go under each component sub-folder such as “blog” as if I were making mini websites?
IRP: you can put it under resources
recommendations on tools for unit test and BDD with angular
IRP: Link provided on slack (https://docs.angularjs.org/guide/unit-testing)
Our Team met as a group at least 2x per week to synchronize and elevate obstacles along our critical path; additionally, individuals teamed up to pair program in order to solve various engineering tasks.
| Date | Meeting Type |
|---|---|
| 12 NOV | Standing Team Meeting |
| 14 NOV | Daily Scrum |
| 15 NOV | Standing Team Meeting |
| 19 NOV | Sprint Review & Retrospective |
- Example of a peer code review (part of our Definition of Done)
- Example of a mob programming (part of our Definition of Done)
- Example of a standing team meeting
We used the cucumber framework and selenium to run our Behavior-Driven Development (BDD) tests. Specifically we tested site navigation using BDD. See the screenshots below (showing test failed and then passed).
BDD source code is checked here: https://github.com/BrainCradle/BrainCradle/tree/master/BDD/BrainCradleTest
Our TDD and unit tests (we have used tool called Karma) are shown below including a failed one and passed ones.
The unit test cases are checked here: https://github.com/BrainCradle/BrainCradle/tree/master/braincradleapp/tests
We conducted our sprint review with stakeholders and Scrum Team retrospective on NOV 19TH.
We reviewed the sprint 1 user story in production Site Nav with our primary stakeholder, Andy.
Andy is pleased with the progress of our efforts. He offered the following feedback, mostly looking towards the next sprint:
- Overall looks clean. Clearly labeled. Font is readable.
- Loves the responsiveness. Woo Firebase!
- Tab highlighting should be added as it doesn't show current tab.
- Dual menu is confusing. Maybe have a standard top bar nav and left hand nav
- Selecting the proper categories under the "Examples Tab" is extremely important. Prefer's the label "Examples" over "Solutions".
- Prefers the term "Real-world Applications" to "Applications".
This feedback will be absorbed into the product backlog (and groomed) ahead of sprint 2 planning.
While the retrospective is a generally closed door event, we chose to share these highlights:
- Angular, Karma & Firebase frameworks had an initial steep learning curve. More pinpointed documentation for features would really help in next sprint. Also framework experts should spend some time walking through the nuances of the code and best practices.
- Despite not being local - the team has managed to leverage tools like slack, google hangouts, conference calls, Trello etc. to collaborate virtually and make progress on the sprint.
- However there is still no substitute to being able to work face to face in person and it took a while for the team to get comfortable and streamline commmunications. We should look for an opportunity to work together on a future sprint in person if circumstances and calendars permit.