Win a copy of Fixing your Scrum this week in the Agile forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Rob Spoor
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Junilu Lacar
  • Tim Cooke
Saloon Keepers:
  • Tim Holloway
  • Piet Souris
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Frits Walraven
  • Himai Minh

Are having waterfall process within a scrum still ok

 
Ranch Hand
Posts: 139
Android Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This is where some requirements are oredefines or out of the box that we already give them the deadline in a sprint.

Let me know your thoughts if this is the case or needs to put things into chunks of user stories in the product backlog
 
Sheriff
Posts: 16564
272
Mac Android IntelliJ IDE Eclipse IDE Spring Debian Java Ubuntu Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What do you mean by this:

Michael Rivera wrote:This is where some requirements are oredefines or out of the box that we already give them the deadline in a sprint.


Please clarify.
 
Michael Rivera
Ranch Hand
Posts: 139
Android Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Some you do not need to estimates because they are already known
 
Junilu Lacar
Sheriff
Posts: 16564
272
Mac Android IntelliJ IDE Eclipse IDE Spring Debian Java Ubuntu Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
ok... so, can you clarify your question? Because I'm still confused. The subject line you gave mentions having a waterfall process in Scrum and your post talks about no estimation because you already know the deadline. In Scrum, estimates are part of the planning toolkit you use to give stakeholders an idea of the answer to their perpetual question, "When will it be done?"

Please restate your question in its entirety so it's clear what exactly you're asking.
 
Michael Rivera
Ranch Hand
Posts: 139
Android Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Im asking if knowing an est8mate before planning still a good approach because it may sound a waterfall approach in a sprint.
 
Junilu Lacar
Sheriff
Posts: 16564
272
Mac Android IntelliJ IDE Eclipse IDE Spring Debian Java Ubuntu Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I guess my confusion is in your equating of "knowing an estimate" and "waterfall". How are you making this connection?

Also, "knowing an estimate" is contradictory. If you know, then you don't need to estimate. If you don't know, then you make an estimate. Again, what is "waterfall" about this? Maybe you need to give a concrete example so we can have some insight into your thought process around this.
 
Saloon Keeper
Posts: 24174
165
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Michael Rivera wrote:Some you do not need to estimates because they are already known



Just because you know the requirements and goals does not mean you can make a waterfall declaration of time. Aside from the fact that the actual time is almost inevitably going to be double or triple what the users will allow you to give*, the point of Agile is that the process is self-modifying and that therefore goals are expected to slip.

And no one really "knows" what they want, least of all the people who ask for it. Before Agile was Agile I learned to sit with the actual users of the system and watch them use it. Often that led to significant improvements and even simplifications.


---
* Ironically, my experience is that the "challenging" parts of a project are not usually where I end up burning up unanticipated time and in fact are often done faster than anticipated. On the other hand, spending 3 days finding that misplaced comma, missing bracket or improperly-captitalized element…
 
Michael Rivera
Ranch Hand
Posts: 139
Android Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes, thus the reason I'm getting your insights with the question.

Agile is agile as what you said, for me at least i use them whenever there is a complex project, and waterfall the known out of the box solutions.
 
Junilu Lacar
Sheriff
Posts: 16564
272
Mac Android IntelliJ IDE Eclipse IDE Spring Debian Java Ubuntu Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Michael Rivera wrote:Agile is agile as what you said


That's not what he said.

Tim Holloway wrote:Before Agile was Agile...


That translates to "Before Agile was even a thing..."

In Tagalog, that translates to something like "Noong hindi pa siya tinatawag na 'Agile' ..."
 
reply
    Bookmark Topic Watch Topic
  • New Topic