Wedding events

Wedding event
  1. Product owner: Ali
Scrum Master: Nasiha
Team Member: Syazwan, Sufi, Ifwat


  1. Catering
  2. Bridal dais 
  3. Wedding Dress
  4. Hall
  5. Photographer
  6. Musician
  7. Florist
  8. Work out your budget
  9. Start the guest list
  10. Arrange transportation
  11. Schedule hair and makeup artists
  12. Photo booth 
  13. DJ
  14. Get printed items
  15. Finalize the day-of schedule


Product Backlog
Person that arrange
Catering
budget, what food they want
Syazwan
Bridal dais
Themes, budget  
Sufi
Wedding dress
Company that will provide the dress
Ifwat
Hall
Reserve the hall, venue
Sihah
Photographer
Package based on their budget
Sufi
Musician
Discuss about genre that will be played during the event
Syazwan
Florist
Decorate the halls based on themes that be chosen
Ifwat
Work out your budget
Discuss about overall budget based on the themes
Sufi
Start the guest list 
Average of the guest list will attend
Sufi
Arrange transportation
Prepare the car for  bride to go the halls
Ifwat
Schedule hair and makeup artists
Package for makeup based on the budget and
Sihah
Photo booth
Reserved the DJ that will come for the event
Syazwan
DJ
Print the card, budget based on the design.
Sufi
Get printed item 
Confirm the schedule of the event
Sihah


Priority
Product Backlog
1
Work out your budget 
2
Hall
3
Bridal dais
4
Wedding dress 
5
Catering 
6
Florist
7
Schedule hair and makeup artist 
8
Photographer
9
Photo Booth
10
DJ
11
Musician
12
Arrange transportation 
13
Start the guest list
14
Get printed items like menu cards and programs designed and printed
15
Finalize the day of schedule


Sprint No.
Product Backlog 
Times 
1
1,3,5,7
2 weeks
2
2,4,6,8
2 weeks
3
9,10,11,13
3 weeks
4
12,14,15 
2 weeks




  1.   
  1. First Scrum Planning meeting
  • The product owner prepares for the meeting by reviewing the most important tasks from the top of the wedding backlog and sharing them with the Scrum Master. 
  1. Daily meeting 
  • Review backlog and discuss the tasks progress, what we need to do today, what happen yesterday and what should do tomorrow.
  • Daily achievement
  1. Review meeting
  • Discuss overall planning and what we accomplished during the sprint.
  1. Retrospective meeting
  • Discuss how we can complete the task in current sprint
  • The scrum team and product owner will discuss about upcoming planning.

Comments

Post a Comment

Popular posts from this blog

Group 1 - Post 2 Iterative Model

Image
Group Members: Siti Shahirah Sabran (01DIS17F1024) Nur Hidayah Zaini (01DIS17F1006) Siti Nurhaliza Ab Aziz (01DIS17F1025) Sharmeela A/P P. Gunasegaran (01DIS17F1008) Siti Ain Zubaidah Syeikh Ahmad Nasir (01DIS17F1007) Noor Fatin Najwa Saharudin (01DIS17F1005) Najmy Izwan Norman Wong (01DIS17F1042) Muhamad Aiman Marzuki (01DIS17F1048) Muhammad Naziruddin Mohd Ahsan (01DIS17F1053) The iterative model is a particular implementation of a software development life cycle (SDLC) Focuses on an initial, simplified implementation, which then progressively gains more complexity and a broader feature set until the final system is complete. In short, iterative development is a way of breaking down the software development of a large application into smaller pieces. Process of Iterative Model Planning Phase : This is the first stage of the iterative model, where proper planning is done by the team, which helps them in mapping out the specifications documents, establish softw
Read more

Reuse-oriented Model (Group 1)

Image
Group Members: Siti Shahirah Sabran (01DIS17F1024) Nur Hidayah Zaini (01DIS17F1006) Siti Nurhaliza Ab Aziz (01DIS17F1025) Sharmeela A/P P. Gunasegaran (01DIS17F1008) Siti Ain Zubaidah Syeikh Ahmad Nasir (01DIS17F1007) Noor Fatin Najwa Saharudin (01DIS17F1005) Najmy Izwan Norman Wong (01DIS17F1042) Muhamad Aiman Marzuki (01DIS17F1048) Muhammad Naziruddin Mohd Ahsan (01DIS17F1053) Reuse-oriented Model The Reuse Oriented Model or The Reuse Oriented Development (R.O.D) is where they reuse programming or software design in previous project. The main idea behind this concept is to reuse software to build higher quality software to make it better and answer the needs of demand. Stages: 1.       Component analysis Based on the requirements specification, components that implement (some part of) the specification are looked for. In the most of the cases there is no exact match and the components that may be used only provide some of the functionality required.
Read more