Re-Visiting Usage Cases and Agile Software Development Cycle / Resume and Job Presentations

 This past week was our last week for Project and Portfolio Five. I am just going to take a moment to mention my experience this month. I will start with my presentation pitch from earlier this month. I had an idea for making a faxing application. But now that we have our chosen Web Application started, I can agree that my Faxing application idea would've been a bit too easy for what is expected for us. Anyway, our team is blowing me away with the quality of work presented. I can honestly say that I am impressed with my team and the work they put into our tasks this month.

Trello serves as a status medium for our project. A medium that allows us to keep updates between each other's work and a good way to track the progress of existing jobs and figure out what should be completed next. With my contributions, I found more work than expected when usage cases needed to be compiled. I found myself looking up online articles and found myself following a template and modeled my scenarios with in it. This is not something bad for us but, it was serving as making my scenarios redundant in the long run when I was thinking up scenarios. I needed to figure out where our Usage cases could live without the user questioning where any of these scenarios may have come from.

Before long I figured out that our Applications A Features (the main features of the app) List would serve as an excellent source for usage cases because, the A features are major indicators of the capabilities of our app. Those features are expected by the user and serves as an indicator about the way the application should work. I used our wireframe to navigate myself through the app and used each step in the flow section of each usage case. I still discovered redundancies within parts of some of the usage case scenarios. I modified the template at this point and used an "Alternative Flow" entry to eliminate some redundancy and this also serves as a nice way to clean up the look of the SDD too.

Later in the application development life cycle, I will need to update the SDD with more Usage cases and satisfy any modification to A, B or C features. All usage cases for the application will need to be found at one point in time. But, as of now, the A features are listed in the current version of the SDD. I will make note to reference my Scenarios and base them off the application wireframe and make sure redundance is at a minimum as I write usage cases in the future.

In conclusion, I want to talk about what's up ahead for me in lieu of writing usage cases. Instead of writing so much, I have been told that, coding and development is going to be a large part of what is expected for us. I am prepared to take on any job that would be presented to me and I would like to have tasks that allow me to present work in a quality and steadfast manner. It appears that most of my team has chosen something they are good at, I other hand am kind of mediocre in any given output or work category. I have expressed my position as "fill" when asked what it is that I can work on. They seemed to have every aspect covered but, I know I will have to work on something and stay busy. This is where the Agile development process should come in. It will give us a way to assign tasks and allow our application an opportunity to be creating with quality in mind. I will be prepared with any task given but, I am nervous until that time for me to get to work and I'd be stuck with nothing to do. I need experience and this idea would be good for us.

On to the next phase of my Project and Portfolio Capstone Project. I appreciate the patience of all those who have helped me so far. I want to be the best at anything that comes my way. I am excited and nervous all at the same time. I will make a point to mention Agile Software Development process with my team. I think it's a great way to introduce a process that most professional companies follow and should help us stay focused along the way! But since it is not required, I won't be disappointed if we don't go this way. I want us to feel comfortable about our work and confident that the output is going to be of good quality standards. So as long as that is the product of our work, I am going with that process. 

This month, I will need to finish my resume, get some job offers and apply to different places. I am definitely nervous about what my degree can bring me with a technology career in the future. I can see myself working and being happy about my job. I deserve that, and i am willing to work hard for it!

Use Cases: What They Are and a List of Examples | Indeed.com

The Agile Software Development Life Cycle | Wrike Agile Guide

Free Online Resume Builder | Indeed.com

Comments

Popular posts from this blog

Authentication token and refraining from using Cron

Long week of Detailing