Final Burndown

Week 10 and 11 Burndown

The Final Week

Our final week had two main focuses:

1. Wrapping up both client websites
2. Preparing for our final sprint review

I met with group members to decide what our final deliverables would be for our client.  With some help from Zoya, I created the team's poster board that was used for our presentation on April 29th.  I also contributed some personal information for our final report. 

Thank you to the team for all your hard work!

Weekly update

This last week we planned out our presentation, and continued working on updating the Arium3D site.
Adam worked on trying to fix the old explorium site, and began working on the final report.

I focused on redoing the graphic for the homepage of the Arium site, so we would have something better than a generic placeholder slideshow. I worked for quite a while to make it an animated image, but ended up not succeeding, so I created a 2D, static version of the butterfly coming out of the card instead. I will continue to work on the image to see if I can make it animated before the end of the semester.

The Final Run

I have delayed this post for the reason of preparing the capstone project report. It is about half-complete with some extra details needed.

The past week, I gathered plenty of materials, facts, and notes taken during meetings to begin writing the repot.

Also the group on Sunday got the site prototype finalized for display on the April 29th presentation, very nice I must say.

Finally, today I managed to get the site back online! I needed to change the themes as their default theme was causing some improper renderings on the CSS end. Unfortunately I had to use IE10 to access the site and get the site updated. I hope no one hacks it...or my computer that is...Ouch.

As the project comes to a close, I wish to congratulate my team members in their ability to adapt quickly and work around the crazy schedules I had. Thank you Gunhee, Jason, Kellie, and Zoya. It's been a fun ride and I hope maybe someday we can do this again sometime (and maybe next time, they'll use our prototypes)...

Final Week

As our final week, the team focused on refining the website to make it look presentable with the limited content/information we had. We added some cool footer widgets to make the website a bit more interactive.

Last Week

We have shifted our focus from Explorium to Arium, in order to have a presentable, working website for our final presentation. I worked on integrating content of the two websites into our new one.. Next week, we will start our project report and keep upgrading our website in terms of functionality and design.

Week of 4/14

Last week I communicated constantly with our client trying to help her focus in on what was were the most important stories to include in our project backlog.  I worked to develop a product page with Gunhee.  We have not been given the okay to put up the client's product on the page so we used all sample pictures.  Gunhee and I also worked on the general appearance and visual appeal of the website.

Under Construction

I have been given the task of updating the Drupal core to the latest version. It's easier said than done since this must be done manually. I did what looked necessary to get the core updated. Most of it is complete, except for some encryption .sql file that I need to make the update of the core AND the site's database go through. This is proving to be a greater challenge but I hope that this week I will figure this out.

Weekly Update

This last week we planned out how we were going to work on our final presentation, and narrowed our focus.

We are now back working on the Arium site, with a few of us working to fix a few problems with the Explorium site before going back to the Arium site and starting to get ready for the final presentation.

We hope to have a functional site, with a working store page as our final deliverable. They may not end up using it, depending on the course the company takes, but we will deliver at least a bare-bones, but functional site for them to start with, if they choose to use it.

Update for 4/17

Kellie and I met up last night to finalize the shopping page. Since our client does not have an actual product yet, we set up a sample page that she will be able to use once she is ready. We have also worked to make the website look cleaner.

Week of 4/7

The weeks really started to jumble together at this point.  Our client informed us that changes were going on within the company and our project scope was changing again.  We no longer needed to add e-commerce to the website because was going to be solely educational. 

Week 7 and 8

Week 8 and 9 burndown charts look the exact same just as week 6 and 7 did. This is because we were given a new backlog. We began working on our user stories and were instructed to stop by our client due to disagreements within the company. 

Week 7 Burndown

The Burndown Chart for week 7 looks the same as week 6.  Our client gave us tasks to work on in week 6 and then stopped our work due to the company restructuring.  

Back to Square One

Well what do we know, we're back at square one. We need to create the shopping page of the site. Right now our largest obstacle is the management within Ariu - Explorium. We have contacted Melody for some things that we need in order for HostGator and Drupal to let us work on the shopping aspect (card encryptions and even the Drupal engine version updates).

Nowhere to go but up at this point, right?

04/14 Week

Last week, I worked on the Secure File Download system on drupal for our website. Initially, there was a difficulty in making drupal accept a valid file path relative to their existing website. Eventually, I decided to keep the path absolute to my computer, instead of relative to the site. During the process of testing, we received an email about stop working on the product/shop page. Our client shifted the site's focus entirely; from e-commerce to educational learning.

This week, the team will meet and decide how to proceed with this project and focus on our final presentation.

Change in project scope

Due to another project scope change, our project is currently on hold until further updates from the client (product owner). We are hoping to find a common ground with the client so that we can find a good way to conclude this project

Another week, another change

This week we continued to work on the website.

I was set in charge of investigating how to encrypt the credit card information so that the store could be set up for people who wanted to use credit cards. Most of the trouble was in figuring out how to use the new interface system, but I had started working out the steps and settings that were needed.

However, our project scope has changed again. We are no longer working on the store page. Instead, we are to focus on creating educational learning pages, with PDF print outs on the various topics.

Another Week

The past couple weeks have been hectic.  Our client and her company has been going through structural changes that have halted our progress.  She has asked us not to disclose any of this information on our class blogs.  Our website updates for one specific website was stopped and we have been directed to work on a new website for the duration of this class.  We did not receive the approval to start working on the new website until earlier this week.  

Update from Client

This past week, I was working on setting up an Shopping page and an Order button/form within the client's website, but then we heard from the client that the project scope has changed. Thus, over the past couple days, we had another meeting with our client to clarify what her expectations were for this project. At this time, it seems like the new scope will be focusing on updating/modifying their current website for the remainder of the project.

Weekly update

This last week, we had continued working on the website and the team met with our product owner on monday. Then, we received an email telling us that the work on the website was no longer needed because of changes within the company beyond our control. We were now back again at square one.

We met with our product owner on Friday and discussed our new direction, which is primarily to work on a more educational focused website and create a shopping cart for that website. A much smaller scope, but one that I believe we can complete by the end of the semester project deadline.

The Search for More Time

Dr. Basham informed us mid-last week that the site we were working on is no longer useful since the organization has undergone some major changes (and possible split?).

This week we plan to help...whatever they want to call themselves get the shopping part of the site operational. Considering all that we worked on, we were going to move on to that this week anyway on the old site.

Let's hope they don't change again after Easter...

Anyways, our ability to adapt and to handle the agile development is going to be put to the test for the rest of the way. Can we do it? I'll go out on a limb to say...yes we will.

Weekly blog

Last week did some hands-on work with making the website on Wordpress. I worked on the "About Us" and "Home" page and created it as decided. I edited the existing content so that it is more concise and readable for the users of the site. My team met with our client, Dr. Basham, but I was, unfortunately, unavailable at that time. This week, I am meeting with the team tomorrow, to talk about what was discussed in the meeting and how we should move forward with our project.

Working on the Shopping Page

This past week and this week, I will continue to work on setting up a shopping page for our client. I am hoping to use a website called Wufoo that helps link order forms to third party vendors (like Paypal) and then we can easily embed it in the website. We have shown our client an example of this and she seemed to like the idea.

Progress

We are finally making good progress on our site.  We have transferred most of the content from the old site onto the new site.  We have researched and discussed with our client how we would like to execute our shopping cart and now have a game plan of how we will execute it.