Mark Breen
marklbreen at gmail.com
Wed Mar 11 10:27:30 CDT 2009
Hello Scrum Team, I have been watching closely the progress Shamil has been making, and wishing I could join, but fearing I may not be able to contribute much. I also see that there are already enough members in the team. However, if you think at this point there is merit, I would like to volunteer to join, perhaps as the product owner. From the recent content from Shamil, I see that it might useful to split these two roles that Shamil currently has ie, Scrum Master and Product Owner. If I am too late, absolutely no offence, I will continue to lurk, but if you want another member, I am available, let me know what your preference it, thanks Mark 2009/3/4 Salakhetdinov Shamil <mcp2004 at mail.ru> > Hi SCRUM team at all, > > Below is the list of forms and reports to develop in Winforms application. > I didn't post the list of Data Access Pages - let's do not develop their > winforms or ReportViewer control reports equivalents in this project? > The subforms/subreports will very probably go togther with their parent > form/report as grids/tables. > > The below list is so called Product Backlog - teh set of > objects/functionality customer/ProductOwner wanted to get developed. > > According to SCRUM/agile and just common sense practices we have to > evaluate the "weight" of every entry in the project backlog. This "weight" > evaluation will be "just" estimation of relative complexity this or that > backlog entry has - and this evaluation/estimation can be expressed in any > measuring units kilograms, litres, kilometres, qty of bananas which could be > eaten while developing this or that form or report etc. > But for customers/ProductOwners will/should be clear that "heavier" entry > will usually be more costly and will usually be developed in longer period > of time than the other "ligher" ones... > > This evaluatiuon/estimation "game" is known in SCRUM as "PLanning Poker > Game", and it shows to be effective and useful "game". > > Please read this short article on "Planning poker game" and related issues: > > http://www.crisp.se/planningpoker > > We have to find a way to "play" this game several times (up to three > usually) until we get the common "compromise" view on the "weight" of > Product Backlog Entries. > > Please note that the first evaluation of "weight" shoudl be as independent > as possible. > > Let's fist talk how we can ogranize this "planning game being" separated by > time and space? > Please do not post any evaluations/estimations here but please correct the > below BackLog if you see some issues with it. > > N.B. Usually nor SCRUM team nor SCRUMMaster do not participate in > preparing/prioritizing of ProductBacklog - the latter is the sole > responsibility of ProductOwner.... > > Thank you. > > -- > Shamil > > P.S. Product Backlog > > Forms > ==== > > 1. Categories > 2. Customer Labels Dialog > 3. Customer Orders > 4. Customer Orders Subform1 > 5. Customer Orders Subform2 > 6. Customer Phone List > 7. Customers > 8. Employees > 9. Main Switchboard > 10. Orders > 11. Orders Subform > 12. Product List > 13. Products > 14. Quarterly Orders > 15. Quarterly Orders Subform > 16. Sales Analysis > 17. Sales Analysis Subform1 > 18. Sales Analysis Subform2 > 19. Sales by Year Dialog > 20. Sales Reports Dialog > 21. Startup > 22. Suppliers > > Reports > ===== > 1. Alphabetical List of Products > 2. Catalog > 3. Catalog Subreport > 4. Customer Labels > 5. Employee Sales by Country > 6. Invoice > 7. Products by Category > 8. Sales by Category > 9. Sales by Category Subreport > 10. Sales by Year > 11. Sales by Year Subreport > 12. Sales Totals by Amount > 13. Summary of Sales by Quarter > 14. Summary of Sales by Year > > > _______________________________________________ > dba-VB mailing list > dba-VB at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-vb > http://www.databaseadvisors.com > >