Project management Agile

+ Redo some of the EPICS and User Stories from week 2

+ Use only 3 user stories to create the tasks in Scrum task board

+ Need to use new user stories for week 3, my user stories are not good

< 2 pages single space

+ Focus on quality work not the length

Extra resources

1. 

Pictorial Comparison of Biological Macromolecules

 –  figures 12-35K and 12-35L.

2. Extra Resources to help you explore enzymes, what they are, how they work, what factors affect enzyme function:  

Factors Affecting Enzyme Activity

, 

Proteins and Enzymes

 (click through all six pages). 

3. 

Video of Buffers

 – don’t get bogged down in the math!

4. 

Understanding Chemical Structure Drawings

Week 2

Heart disease is the leading cause of death among people in the United States.  Approximately 25% of deaths in this country can be attributed to heart disease (

CDC Heart Disease Fact Sheet

).  Fast food contains a significantly high amount of unhealthy fats, which contribute to the development of heart disease.  In recent years, there have been several local governments that have taken action to reduce the amount of trans fat found in the fare from local fast-food restaurants.  New York City was the first to enact regulations on fast food in 2005. An overview of the regulations in place on fast foods in New York City can be found in 

Time Article on Soda Ban

. In 2008 Los Angeles banned the building of new fast-food restaurants. This past fall,

 Berkeley, CA banned candy and junk food 

in grocery store checkout aisles.

In 2015, the FDA released its final determination on partially hydrogenated oils (trans fats):  

FDA Final Determination Regarding Partially Hydrogenated Oils

.  Here are two news articles that came out when the new ban was released: 

CNN

, 

The New York Times

.  

Given what you are learning this week about macromolecules, and based on your own experiences and research address the following scenarios and questions.

1. A Fast food chain is being sued for producing a harmful product.  You are a juror sitting on this trial.  How would you vote?  Why? Are manufacturers of unhealthy food responsible for the health consequences of their products, and if so to what extent?  

2.  Is it appropriate for local, state, or federal governments to enact legislation regulating fats and sugars found in foods sold at fast-food restaurants?  What about foods found in the grocery store or at other restaurants?  Why? Why not?

Be sure to site and all websites you use for references.

Comment meaningfully on at least three of your classmates’ posts.

Running head: SCRUM PROJECT 1

SCRUM PROJECT 3

Product Vision

Elevator Statement: Lizard Farm is an insurance company with products that entail home and auto insurance. Our company also offers tracking for claims, customers and premium payments. The product ensures that claims once recorded and approved instigate claim payments in the shortest time possible. The insurance product is effective, affordable and discounted once a client applies for both home and auto insurance.

High-Level Product Backlog with 4-5 Strong Epics. Release Schedule (this will be an estimate)

The high-level product backlog for Lizard Farm entails the following epics starting with the highest priority item.

Premium tracking: The system will track premium payments and this epic can be broken down into premium recording and discounting for clients who have purchased both home and auto insurance products. It will take a period of four weeks to release and will recur after another four weeks.

Customer tracking: The system will track the risk level for clients and this epic can be broken down into customer profiling and customer risk analysis. This will take a period of three months to release and will happen every four weeks (Sprint 1).

Claim tracking: The system will track client claims and this epic will entail claim analysis and claim schedule recording (Rubin, 2012). This will take four weeks to release and will happen every four weeks (Sprint 2).

Claim recording: The system will record claims and this epic entails claim number assigning and claim follow up. This will take four weeks to release and will happen every four weeks (Sprint 3).

Claim payments: The system will make payments for approved claims and will entail claim payment recording. This will take four weeks to release and will happen every four weeks (Sprint 4).

Who needs to be on your team? Include yourself as the Scrum Master.

I will be the scrum master for my team. The team will entail the scrum master, the product owner, and the development team, the CFO, agile lead, product manager, designer, marketing manager, analyst, procurement manager. The scrum master will be responsible for guiding the team in following and creating their own process as per the general scrum framework. The product owner will be responsible for the order and components of what is to be developed for the Lizard Farm project (Rubin, 2012). The development team will be responsible for figuring out how to deliver what has been asked for by the product owner.

How long will your sprints be? How did you decide this?

The project sprints will be four weeks long. Each sprint will start on the first day of the month and end after four weeks i.e. on the 28th. However, there will be a few days from 28th to 30th or 31st that will be added as part of the four week period according to the calendar month. That is to say that an epic that is due to be delivered in four weeks can be delivered on the 31st of that month, for instance. The decision to have four-week sprints is to allow as much time as possible for clients to make claims and for the company to track and record these claims. For instance, if a claim is made on the first of the month, it will be tracked, recorded and if approved, payment will be done by the 31st of that month. All sprint periods for all epics will be equal and they are set as such to allow for tangible results for the client after each sprint period (Rubin, 2012). Additionally, for the company to deliver on the clients’ needs.

References

Rubin, K. S. (2012). Essential Scrum: A practical guide to the most popular Agile process. Addison-Wesley. Retrieved from

https://books.google.com/books?hl=en&lr=&id=3vGEcOfCkdwC&oi=fnd&pg=PR11&dq=Essential+Scrum:+A+Practical+Guide+to+the+Most+Popular+Agile+Process+By+Kenneth+S.+Rubin&ots=-CDfom9v2p&sig=0ExIcZ7ZZaVcseFjboArMcSOj5M

Lizard Farm – We’re working to keep your money…

Insurance Management System (IMS)
Project
Description
New system needed within a year or so, to handle all aspects of our company’s insurance business. We

operate in all 50 states. We handle auto insurance and home insurance, and offer discounts if you use

us for both together. We do not do life insurance: apparently, everyone dies at some point.

The system must do at least the following:

 Claim recording

o For Example: If I have a car accident or a storm destroys the roof of my home I need to

alert Lizard Farm.

 Claim tracking

o For Example: Lizard Farm needs to track that car accident or destruction to my home, so

different people in the company have access to it.

 Claim payments

o For Example: Lizard Farm must pay me for the damage caused to my car in a reasonable

amount of time.

 Customer tracking

o For Example: Lizard Farm must be able to track customers, so they can determine if a

customer is “high risk” – such as constant car accidents.

 Premium tracking

o For Example: Lizard Farm needs to know if customers are paying their premiums.

General Assignment Notes
You will be expected to do some research here into the nature of Insurance companies and what they

do, but you are not expected to become an expert in software of that type. You should be able to

identify with and perhaps enhance the list above, but that is primarily to give you a fertile field for

picking User Stories for the project. I am more interested in how you communicate your thinking, both

to me, to your fictional team, and to the senior organization people that need convincing that Agile is

viable.

Remember the marking standards! If you do exactly what the assignment asks for, you will get a good

solid B+ (85%). To get an A, you must exceed expectations without going beyond the assignment

boundaries – for example, if you include a detailed project schedule with the first assignment, you will

probably lose points!

Below is the general assignment breakdown – each week will contain details on the specific assignment.

All weeks will be open, so you are welcome to “look ahead” to see what the upcoming assignment will

be about.

Assignment 1
Produce Agile Justification Memo

Assignment 2
High-Level Product Plan and Epics

Assignment 3
Completed Sprint Plan and Backlog.

Assignment 4
Relative Estimation and Task Board