<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Fantastic Four Acebook Project - Medium]]></title>
        <description><![CDATA[Makers Academy — Week 8 — Documenting our learning from a groupwork project - Medium]]></description>
        <link>https://medium.com/fantastic-four-acebook-project?source=rss----9dabcdad37a1---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Fantastic Four Acebook Project - Medium</title>
            <link>https://medium.com/fantastic-four-acebook-project?source=rss----9dabcdad37a1---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:07:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/fantastic-four-acebook-project" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Sprint 5 — The Last Blog!]]></title>
            <link>https://medium.com/fantastic-four-acebook-project/sprint-5-the-last-blog-2d28148d8fb2?source=rss----9dabcdad37a1---4</link>
            <guid isPermaLink="false">https://medium.com/p/2d28148d8fb2</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[codingbootcamp]]></category>
            <dc:creator><![CDATA[Hanna Aikas]]></dc:creator>
            <pubDate>Thu, 19 Sep 2019 20:27:39 GMT</pubDate>
            <atom:updated>2019-09-19T20:27:39.157Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Sprint 5 — The Last Blog!</strong></h3><p>All good things must come to an end…</p><p>Russ volunteered to be Scrum Master for our last 2-day sprint, and I volunteered to be Blogger. I should clarify that “Blogger” is not an official role under Scrum methodology, it’s a role that our team invented in order to document our learning…</p><p>So, what happened in our last sprint?</p><p>We kicked off the morning with a really strong stand-up meeting, which our Scrum Master had prepped on the previous evening. He had gone through the bother of splitting out tickets and thinking through the current user journeys for our app. Hence, we were all greeted with a delightfully clear diagram on a whiteboard, as shown in the picture below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a0T3IHmQcyACg-SxleGyOQ.jpeg" /><figcaption><em>Scrum Master Russ and Equally Important Person Kriss admiring the whiteboard</em></figcaption></figure><p>We kicked off our stand-up meeting with the usual check-in, this time “Which book/film describes how you feel this morning”…</p><p>· Hanna — Brave New World (book — both in the optimistic sense, and the dystopian sense)</p><p>· Farnaz — Eat Pray Love (Farnaz’s favourite film ever)</p><p>· Kriss — Quiet (best book ever for introverts) and Good Will Hunting (best film ever)</p><p>· Russ — Catcher in the Rye (strange book choice, I forget the reason why, maybe Russ is trying to shoot John Lennon) or Atlas Shrugged (book about people who get sh*t done)</p><p>We quickly realised during the stand-up meeting that we had more tickets then we could possibly handle, given we had only 1.5 days left, and that time would also be interrupted by various other very important things like the CV workshop and 121s with coaches.</p><p>Hence, we prioritised ruthlessly — Farnaz and Kriss picked up the big ticket on implementing a Friends feature (which we were all super excited about) whilst Hanna and Russ picked up a ticket about users posting on their own wall vs. other users’ walls vs. the “big wall” that shows everyone’s posts. We were feeling so optimistic that we even discussed what other tickets we could pick up from the “bit ’n’ bobs” section once we finished our allocated tickets…</p><p>Oh, how cute.</p><p>With hindsight — it’s great to have optimism and ambition, but actually both our tickets turned out to be rather demanding. Farnaz and Kriss had an early break-through, but then hit a minor hitch that took up a lot of time. Meanwhile, Hanna and Russ got off to a decent start, then had a brain wave about how to do the job “properly”, decided that would be impossible given time constraints, then proceeded to hack their way through to something acceptable.</p><p>Earlier in the day, some hesitation had emerged on the topic of “what, we have to do a presentation tomorrow?…”. But we decided to shelve that concern for now, just focus on getting stuff done between now and Friday mid-day, and then figure out the presentation on Friday at 2–3pm. This was the only rational option, seeing as we would only receive instructions about the presentation on Friday morning, so no point worrying about tomorrow’s problem.</p><p>As I write this text, it is now Thursday 9pm, and I know you’re all dying to hear how it went on Friday… Did the final version of the app work? Was it awesome? Did the presentation blow everybody’s minds?</p><p>Sadly, you will never know. This morning we decided that the duties of “team blogger” end tonight, so there will be no further blogs.</p><p>If you really want to know how the story ended, you’ll just have to offer one of us a job as a software developer and then we promise to tell you the end… Find us on linkedin/twitter/elsewhere.</p><p>It’s been wonderful! Yours truly,</p><p>Farnaz</p><p>Hanna</p><p>Kriss</p><p>Russell</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d28148d8fb2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fantastic-four-acebook-project/sprint-5-the-last-blog-2d28148d8fb2">Sprint 5 — The Last Blog!</a> was originally published in <a href="https://medium.com/fantastic-four-acebook-project">Fantastic Four Acebook Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sprint 4, Day 1]]></title>
            <link>https://medium.com/fantastic-four-acebook-project/sprint-4-day-1-5791c2b10a15?source=rss----9dabcdad37a1---4</link>
            <guid isPermaLink="false">https://medium.com/p/5791c2b10a15</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[codingbootcamp]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Kriss Wiltshire]]></dc:creator>
            <pubDate>Wed, 18 Sep 2019 07:21:13 GMT</pubDate>
            <atom:updated>2019-09-18T07:21:12.733Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Scrum Master:</strong> Farnaz</p><p><strong>Blogger:</strong> This guy</p><p><em>The others: Russ and Hanna</em></p><p><strong>Quote of the day:</strong></p><p>“Failure is nothing more than a chance to revise your strategy”</p><p><strong>Stand-up:</strong></p><p>Check-in — what’s your Disney character based on your mood today?</p><ul><li>Farnaz — Arial</li><li>Kriss — Arial ( Farnaz copied me..)</li><li>Hanna — Baloo</li><li>Russ — Aladdin</li></ul><p>What we did:</p><p>Today we focused on the feedback that we received from Sophie (Product owner). This turned out to be more difficult than first thought but the criteria was eventually met. We are all looking forward to working on the new criteria.</p><p>Go team!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*UceStfUyv9RCdzkTSdl16A.jpeg" /></figure><p>Sophie’s Feedback:</p><ul><li>Would like users who are not logged into to be redirected to the “/” route and see the sign up/sign in options there.</li><li>Should be able to see all posts in the “/” route when logged in, and my own posts in a /users/:id route</li><li>Couldn’t test not being able to edit or delete another users posts because I can’t see other users posts</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5791c2b10a15" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fantastic-four-acebook-project/sprint-4-day-1-5791c2b10a15">Sprint 4, Day 1</a> was originally published in <a href="https://medium.com/fantastic-four-acebook-project">Fantastic Four Acebook Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sprint 3, Day 2]]></title>
            <link>https://medium.com/fantastic-four-acebook-project/sprint-3-day-2-178f407f79da?source=rss----9dabcdad37a1---4</link>
            <guid isPermaLink="false">https://medium.com/p/178f407f79da</guid>
            <category><![CDATA[codingbootcamp]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[F Ardenti]]></dc:creator>
            <pubDate>Tue, 17 Sep 2019 07:31:38 GMT</pubDate>
            <atom:updated>2019-09-17T07:31:38.480Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Scrum Master:</strong> Hanna</p><p><strong>Blogger:</strong> Farnaz</p><p><em>Equally Important Team Players: Kriss and Russ</em></p><p><strong>Stand-up Meeting Agenda:</strong></p><p>Check-in: what music genre do you feel like today? <br>What did you learn since last meeting?<br>What wold you like to work on?<br>Possible blockers?</p><p><strong>Planning:</strong></p><p><strong>A. Objectives</strong></p><p>What do we want to aim for today?</p><p><strong>B. Trello &amp; Work allocation</strong><br><strong>C. Schedule for today</strong></p><p>Retro at 3:30pm</p><p>Process Workshop at 4:00pm</p><p><strong>What we did:</strong></p><p>After our weekend challenge reviews, we talked about our plan for the day and what we would like to work on. We checked the board and decided to work on outstanding tickets and try to complete all tasks on the board today and from the next Sprint (tomorrow) we will add more tickets to the board based on Sophie’s (our Product Owner) review on Friday and the next requirements that we will get.</p><p>We managed to finish all tasks but found out that we have to make some alterations to the application as it wasn’t meeting the full specs of the requirements for showing posts.</p><p>We had our end of Sprint retro where we talked about our day and how are we feeling about our progress and what we would like to focus on.</p><p><strong>Review from Sophie:</strong></p><p>- Nice to see consistent logging on the blog, can really get a sense of how the team is working together.<br>- Looks like you’re starting to get ready for some new requirements, remember to ask me for a review<br>- Try to add acceptance criteria for every ticket, to make sure everyone on the team has a shared understanding of what the ticket means.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=178f407f79da" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fantastic-four-acebook-project/sprint-3-day-2-178f407f79da">Sprint 3, Day 2</a> was originally published in <a href="https://medium.com/fantastic-four-acebook-project">Fantastic Four Acebook Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sprint 3, Day 1]]></title>
            <link>https://medium.com/fantastic-four-acebook-project/sprint-3-day-1-17c44f453111?source=rss----9dabcdad37a1---4</link>
            <guid isPermaLink="false">https://medium.com/p/17c44f453111</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[group-work]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[F Ardenti]]></dc:creator>
            <pubDate>Mon, 16 Sep 2019 07:37:51 GMT</pubDate>
            <atom:updated>2019-09-16T21:41:31.710Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Scrum Master:</strong> Hanna</p><p><strong>Blogger:</strong> Farnaz</p><p><em>Equally Important Team Players: Kriss and Russ</em></p><p><strong>Stand-up Meeting Agenda:</strong></p><p>Check ins: what animal do you feel like today?<br>What did you learn since last meeting?<br>What wold you like to work on?<br>Possible blockers?</p><p><strong>Planning:</strong><br><strong>A. Objectives</strong><br>What do we want to aim for today?<br>- Close out tickets -&gt; demo to Sophie -&gt; get new requirements?<br>and/or<br>- Focus on Sophie’s feedback from yesterday?<br>and/or<br>- Focus on Engineering Project Criteria?<br><strong>B. Trello &amp; Work allocation</strong><br><strong>C. Schedule for today</strong></p><p><strong>What we did:</strong></p><p>At our stand up we spent some time looking at photos of neckless baby Hipos and cute Pangolins as we started our check ins. Then we discussed our card wall and prioritised tasks. We also created tickets on the board from Sophie’s feedback.</p><p>Kriss and Farnaz worked on the ticket for “users can update posts (MEDIUM)”</p><p>Hanna and Russel worked on updating the README file and ticket for “Posts appear with newest post first (Small)”</p><p>We decided to have our first group lunch today.</p><p>After lunch we continued completing our tickets. At then end of the day we had a meeting to discuss the week, our app, whats outstanding and how we felt about everything this week.</p><p><strong>Review from Sophie:</strong></p><p>Testing<br>- 90% or greater test coverage. — Yes<br>- Unit tests — No, some evergreen tests for the controller and models. Would like to see more comprehensive unit and integration tests<br>- Every feature is tested from the user’s perspective. — Yes</p><p>Good distribution of work<br>- Every member of the team has made commits — Yes, aim for more even distribution of work<br>- Every completed ticket has a closed (or merged) Pull Request — Yes, think so</p><p>Quality of work<br>- Commit messages are clear and composed of: — Yes<br>- a single line describing the changes made.<br>- a description of the problem it solves, with reference to the user.<br>- The Linter passes on all commits. — 1 offence on master, make sure your CI runs the linter<br>- All commits have a low complexity score. — Not sure, add a button to your README<br>- All pull requests are peer reviewed. — Yes, but look into add an Approval set to your workflow in GitHub</p><p>Documentation<br>- There is up-to-date documentation:<br>- a project description. — Yes<br>- how to install and run it. — Yes<br>- how to run tests. — Yes</p><p>Comments<br>- Nice to see some commenting on the PRs<br>- Overall the quality of processes seems to be high, just make sure you’re using unit and integration tests as well as feature tests when writing code.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17c44f453111" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fantastic-four-acebook-project/sprint-3-day-1-17c44f453111">Sprint 3, Day 1</a> was originally published in <a href="https://medium.com/fantastic-four-acebook-project">Fantastic Four Acebook Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sprint 2, Day 2]]></title>
            <link>https://medium.com/fantastic-four-acebook-project/sprint-2-day-2-611f5350d4c0?source=rss----9dabcdad37a1---4</link>
            <guid isPermaLink="false">https://medium.com/p/611f5350d4c0</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Hanna Aikas]]></dc:creator>
            <pubDate>Thu, 12 Sep 2019 19:39:30 GMT</pubDate>
            <atom:updated>2019-09-12T19:39:30.361Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/708/1*CbDDd5zYtXa6PCywPY200g.png" /></figure><p><strong>Stand-up Meeting Agenda:</strong></p><p>- Check ins- give your theme song for the morning</p><p>- One thing you have learnt</p><p>- What you want to work on</p><p>- Possible blockers</p><p>Then:</p><p>- Review yesterday/merge requests</p><p>- Choose tickets for the day</p><p>- Split tickets</p><p>- Assign pairs/branch names</p><p><strong>Agreed in Stand-Up Meeting:</strong></p><p>- Lessons Learned: When planning, decide what names we’ll give each branch, and put branch name in Trello ticket</p><p>- Open Questions: Ask Sophie (coach) about how the Router fits in with the MVC model (MVC stuff is in app folder, router is in config folder of our Rails app)</p><p><strong>Key Points from Q&amp;A with Sophie:</strong></p><p>- In Rails, do we need to do Unit Tests (to test stuff that Rails builds for us) or focus more on Feature Tests? Answer: Focus on Integration Tests and Feature Tests. Integration tests are testing interaction between controller/model/database, but they leave out the browser (unlike a Feature Test which also involves the browser).</p><p>- [See above question on MVC + Router]. Answer: The router changes the routing that has been set up when we implemented a given Rails scaffold. To find out what the ‘root’ does (e.g. ‘posts#index’), click on the link right below it in the comments! To understand full MVC model, see link below (at end of blog — link from Farnaz).</p><p>- What do CI tools actually do? You set it up to run the linter and the tests, and your code will not deploy to production until these pass. Have to tell the CI tool how to build your app. Common errors:</p><p>o Bundler version dependencies</p><p>o Gemfile missing dependencies</p><p>o Enviroment settings production/development/tests</p><p><strong>What we did - morning &amp; afternoon shift:</strong></p><p>- Not a full day, as we had Q&amp;A at 11 and careers talk at 3pm. So we effectively just did a half day</p><p>- Farnaz and Hanna worked on database — set up associations — one user has several posts.</p><p>- Kriss and Russ worked on closing out remaining tickets on sign in, sign up, routing. Also picked up new ticket on adding line breaks to posts.</p><p>- All tickets completed and moved to In Production by end of shift! Wooohoooo!</p><p><strong>Feedback from Sophie:</strong></p><p>- Make sure your README is up to date, and would be useful to anyone joining the project tomorrow</p><p>- Nice to see lots of closed PRs, consider putting in place an approval check point on GitHub and protecting the master branch so it can’t be pushed to.</p><p>- Would also be great to see more discussion on PRs, you can comment on the PR as a whole or on individual lines of code. Can speed up workflow and help make sure everyone understands the code.</p><p><strong>End of Sprint Retro — Key stuff:</strong></p><p>- <strong>What went well in sprint?</strong></p><p>o Through experience we improved as a team vs. Sprint 1</p><p>o Sat close to each other</p><p>o Did branches well on Day 2</p><p>o Did Trello tickets well on Day 2 -&gt; clarity</p><p>o Positive vibes!</p><p>-<strong> What to improve?</strong></p><p>o Even workloads / swapping driver role / committing</p><p>- <strong>Favourite feature in our app?</strong></p><p>o Line breaks in posts</p><p>o 1-to-many relationships</p><p>o All the Travis stuff, Linter, Tests pass!</p><p>- <strong>What to improve in our app?</strong></p><p>o Styling</p><p>o Refactor tests, adding helpers</p><p><strong>Notes — Technical resources:</strong></p><p>- From Russ: Article on how to create associations between 2 Active Record Models: <a href="https://guides.rubyonrails.org/association_basics.html">https://guides.rubyonrails.org/association_basics.html</a></p><p>- From Farnaz: Picture on MVC model incl. DB and router: <a href="http://images.thoughtbot.com/ember-rails-terminology-differences/rails.png">http://images.thoughtbot.com/ember-rails-terminology-differences/rails.png</a></p><p>- From Kriss: command to access the heroku database: heroku pg:psql</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=611f5350d4c0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fantastic-four-acebook-project/sprint-2-day-2-611f5350d4c0">Sprint 2, Day 2</a> was originally published in <a href="https://medium.com/fantastic-four-acebook-project">Fantastic Four Acebook Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sprint 2, Day 1]]></title>
            <link>https://medium.com/fantastic-four-acebook-project/sprint-2-day-1-eabb3d3205c1?source=rss----9dabcdad37a1---4</link>
            <guid isPermaLink="false">https://medium.com/p/eabb3d3205c1</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Hanna Aikas]]></dc:creator>
            <pubDate>Wed, 11 Sep 2019 19:38:58 GMT</pubDate>
            <atom:updated>2019-09-11T19:38:58.806Z</atom:updated>
            <content:encoded><![CDATA[<p>After the fantastic 1st blog post from Russ, I’m going to lower the standards a bit!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RaHekHK81t98PE8PyOQ6fw.jpeg" /><figcaption>Russ being the boss (and proving that he doesn’t look like himself in photos). He’s pointing at the thing Hanna &amp; Farnaz were not meant to work on in the afternoon!</figcaption></figure><p>Key stuff we did / learned today:</p><p><strong>Roles for sprint 2:</strong></p><p>- Scrum Master = Russ</p><p>- Blogger = Hanna</p><p>- Equally Important Team Players = Farnaz &amp; Kriss.</p><p><strong>Agenda for stand-up (posted on Slack by Russ):</strong></p><p>- Check-ins: give the food that reflects your state.</p><p>- One thing you have learnt since last meeting</p><p>- One thing you want to work on this sprint</p><p>- Possible blockers</p><p>Then:</p><p>- Decide on tickets; Split tickets</p><p>- Choose the one task to mob</p><p>- Assign pair tasks; Assign pairs</p><p>- Separate for mob research</p><p><strong>How the stand-up went:</strong></p><p>- Russ brought a magic frog — whoever holds the frog speaks!</p><p>- Meeting went well except Farnaz was stuck in commuting hell (trespasser on line…)</p><p><strong>Feedback from Sophie (Makers coach):</strong></p><p>Good stuff:</p><p>- Mood check-ins</p><p>- Rotating roles</p><p>- Fitting in own work e.g. stop at 4:30pm for process workshop</p><p>- The magic frog!</p><p>- Looking at Trello board in meeting</p><p>Stuff to improve:</p><p>- Too many items on Trello board “In progress” column</p><p>- Hesitating at estimating ticket sizes — just guess, refine later</p><p><strong>What we did — morning shift:</strong></p><p>Kriss &amp; Hanna read up on Rails. Russ &amp; Farnaz tried to fix Travis issue.</p><p>Attended a Q&amp;A lead by Katerina.</p><p>Then split into pairs:</p><p>- Russ &amp; Kriss sorted deployment issues (Travis / Heroku)</p><p>- Farnaz &amp; Hanna did user authentication. Also, Farnaz got help from Katerina on testing, Hanna asked Sophie to clarify user requirements.</p><p><strong>What we did — afternoon shift:</strong></p><p>Caught up after lunch, then split up into pairs again. BUT being a bit of a fool, I forgot which task which pair were working on, so led my pair to work on the same damn thing as the other pair… Oops. Apparently it was fixed in the end, will find out in tomorrow’s stand-up.</p><p><strong>Summary</strong></p><p>Good stuff:</p><p>- Stand-up meeting</p><p>- Pairing</p><p>- Got stuff working in the end</p><p>- Forgiving when someone screws up…</p><p>Room for improvement:</p><p>- Being 100% sure who is working on what (make it idiot-proof!)</p><p>- Co-authoring git commits…</p><p><strong>Notes / Technical resources:</strong></p><p>- From Russ: walkthrough we used for generating sign up via devise in Sprint 1: <a href="https://medium.com/@mchisti/creating-simple-users-in-rails-with-devise-gem-tutorial-cd91d2ef36d5">https://medium.com/@mchisti/creating-simple-users-in-rails-with-devise-gem-tutorial-cd91d2ef36d5</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eabb3d3205c1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fantastic-four-acebook-project/sprint-2-day-1-eabb3d3205c1">Sprint 2, Day 1</a> was originally published in <a href="https://medium.com/fantastic-four-acebook-project">Fantastic Four Acebook Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sprint 1]]></title>
            <link>https://medium.com/fantastic-four-acebook-project/sprint-1-963ada59b2be?source=rss----9dabcdad37a1---4</link>
            <guid isPermaLink="false">https://medium.com/p/963ada59b2be</guid>
            <category><![CDATA[group-projects]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[learn-to-code]]></category>
            <category><![CDATA[group-dynamics]]></category>
            <category><![CDATA[makersacademy]]></category>
            <dc:creator><![CDATA[Russell Wind]]></dc:creator>
            <pubDate>Wed, 11 Sep 2019 11:37:05 GMT</pubDate>
            <atom:updated>2019-09-11T11:37:05.073Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/550/0*2f1Px5rVsHV3TwDj.png" /></figure><h3>Group Engineering Project Startup</h3><p>Here we go again! Another day another project. This time We would be producing a social media site but had a bit longer for this one: 2 weeks. everything should be built in rails.</p><p>Looking at the other groups as well it seemed we were the only group of 4 with every other team having two extra members. With our streamlined group we set about achieving some tasks:</p><ul><li>Forking the project, a partially constructed version of rails.</li><li>Setting up our Trello board and documentation.</li><li>Deciding who would be scrum leader/blogger for the first sprint (Kriss/Me).</li><li>Setting our schedule for the day.</li><li>Some independent research into Rails (this was new for all of us)</li><li>Ensuring that the app could at least display hello world.</li><li>Splitting some of the tasks into smaller chunks.</li><li>Assigning tasks for the first sprint (CI and deployment)</li><li>After a lot of effort and even more error messages, Travis CI came up green and we were off with Continuous Integration.</li></ul><h3>Sprint 1 Recap:</h3><p>Our first sprint was over and all of us felt like we had learnt a huge amount. Rails seems to have a steep learning curve but once you can get over the size of the whole thing you realise that it is that big so that it can automate repetitive tasks so you can concentrate on the harder stuff. We also had the added bonus of Continuous Integration and Deployment constantly laughing at us as we attempted to commit new code. Still some of our tickets were completed.</p><p>We had managed to get Heroku and Travis set up and running. Also our linter, quality checks and coverage were all up. We also had signing in functionality via devise however this had triggered some issues in CI. I guess we would be out of a job if it all ran smoothly though.</p><p>After our afternoon retro the group had some feedback:</p><p>Positives: Everyone in the group was engaged in the task and keen to do well. Even though we had a smaller group than the others we seemed to have managed to get a decent amount done and everyone had learnt a lot. We were also pretty happy with how our pair programming had gone, everyone was contributing.</p><p>Areas to improve: Although our first mobbing session on Monday had gone well we were not so effective when we had an impromptu session on the Tuesday. We were all pretty enthusiastic about the task but this did lead to some talking over each other and flow issues. We also wanted to improve how we shared what we learn’t day to day.</p><p>Tomorrow we will try out a couple of things:<br>Take 20–30 minutes before a mobbing session to research the topic we will attempt and then share what we have learnt as a group.<br>Each explain one skill that we have learnt to the others, then identify one area we struggled in and try to identify the blockers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=963ada59b2be" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fantastic-four-acebook-project/sprint-1-963ada59b2be">Sprint 1</a> was originally published in <a href="https://medium.com/fantastic-four-acebook-project">Fantastic Four Acebook Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kick-off!]]></title>
            <link>https://medium.com/fantastic-four-acebook-project/kick-off-f6e0c0448d37?source=rss----9dabcdad37a1---4</link>
            <guid isPermaLink="false">https://medium.com/p/f6e0c0448d37</guid>
            <dc:creator><![CDATA[Hanna Aikas]]></dc:creator>
            <pubDate>Mon, 09 Sep 2019 11:08:20 GMT</pubDate>
            <atom:updated>2019-09-09T11:08:20.104Z</atom:updated>
            <content:encoded><![CDATA[<p>This blog will be used to document our learning from the AceBook project.</p><p>Our team is called Fantastic Four, and we are:</p><p>Kriss Wiltshire<br>Russell Wind<br>Hanna Aikas<br>Farnaz Ardenti</p><p>First update coming soon!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6e0c0448d37" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fantastic-four-acebook-project/kick-off-f6e0c0448d37">Kick-off!</a> was originally published in <a href="https://medium.com/fantastic-four-acebook-project">Fantastic Four Acebook Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>