Inner workings of a team

The past week was just a mad rush to get the app up from scratch. Not having the experience in the framework we used made it worse. Each of our team members were tasked to do very different/separate features, and i was tasked with the back-end and eventually bringing them all together. It's definitely not something i've done before - firstly, building something up from scratch, and secondly, having to coordinate with others to piece all the parts together. While not executed perfectly, I'm quite happy that we managed to get things up and running (even though it might still be rather minimal).

The SCRUM talk was quite interesting and gave me a fresh perspective towards how a team should work. This workflow seems to tie in very well with agile software development in terms of setting defining specific milestones for releases - building the app up bit by bit and slowly evolving it. While we have tried using scrum in our workflow, i can't say we have gotten very much into it considering the time span we've been working on it and how hectic it has been this past week. Regardless, i'm still looking forward to see how it will play out in the next two weeks when finishing up assignment 1. 

While i do think that agile software development is good in terms of building up small apps, I realize that this is definitely not wise to do so for the schema. Having to design the schema, i realize that one must have a good idea of what we want the app to do/support, and more importantly, have an idea on what we want the app to evolve towards in the future. Having a bad schema design definitely doesn't bode well when we realize we will need to run redesign tables and links when we want to add in a new feature, especially when it comes to agile software development.

In terms of the concept for our app, I feel that while certain aspects have been done before, the core features that we want to support definitely puts a new spin on things. The only thing i worry about is whether or not this new spin would be appealing to others.

Comments

  1. Unknown5 September 2017 at 15:02

    After the mid term submission your application has probably fixed one of the biggest feature and got it done out of the way, hope you polish up your application!

    ReplyDelete

Post a Comment

Popular posts from this blog

Thoughts on Mendeley

The presentation on Mendeley was well executed and I feel that the presentation, as a whole, leaned towards the good aspects of the app. Firstly, they emphasized mainly on how Mendeley facilitates online research collaboration between peers. They juxtaposed Mendeley and other collaborative apps such as Google Drive, bringing across how Mendeley takes things a step higher to provide better functionalities to the user in terms of collaboration. I would say that this is the main crux (or selling point) of the app, and they did a good job in convincing us on how Mendeley is clearly superior on this front. Secondly, they talked about how there is a lack of real time syncing for the app, as compared to other traditional cloud services which does this for us normally. It was emphasized that real time syncing has become a default expectation for users nowadays and hence should not be missing from its implementation. I feel that this is quite significant, but not mainly because it has becom
Read more

Steam Desktop UI needs to get its priorities right.

Image
The landing page of Steam's desktop application sends you straight to Steam's store, which is a mess of buttons, options and images, which is quite the turn off. As I frequently use the application to access my games on Steam, it always irks me to have to go through this page. Users don't buy games on a daily basis, so it doesn't make sense that Steam's landing page should be it's store. It almost seems as though it was a design decision aimed purely at earning more money instead of improving the user's experience. In addition, the page itself seems to be extremely choppy, likely due to the large number of images / videos it needs to process. In fact, it does remind me a little of yahoo's landing page, albeit worse - a classic example of having too many things going on on a single screen. Which reminds me of a talk I attended before on UI/UX a while back, the speaker (Su Yuen) mentioned that for each screen on the application, choose only 3 m
Read more