The chat will last about an hour and we use the #DevDiscuss tag.
Rules:
- Stay on topic
- ALWAYS ALWAYS use hashtag #DevDiscuss
- Be NICE/POSITIVE ❤️
- Quoting tweets for clarity is encouraged
(ALWAYS use the #DevDiscuss, even on replies where appropriate 😄)
I don't believe in Feature Creep. The very term implies you knew everything when you started (which you can't). It's what you learn along the way. #DevDiscuss.
I don't believe in Feature Creep. The very term implies you knew everything when you started (which you can't). It's what you learn along the way. #DevDiscuss.
Feature creep is when you agree to a predetermined list of features and keep adding to it. And the usually have a conversation around why the original deadline was not met. 🙁 #DevDiscuss
I don't believe in Feature Creep. The very term implies you knew everything when you started (which you can't). It's what you learn along the way. #DevDiscuss.
I think of feature creep as the state of allowing features to pile into a product without enough discernment. We hope each new feature will finally bring the experience we're looking for.
All at the expense of UX simplicity and maintainability #DevDiscuss
I don't believe in Feature Creep. The very term implies you knew everything when you started (which you can't). It's what you learn along the way. #DevDiscuss.
Feature creep killed my job when management kept giving one customer what amounted to design and feature control over our product. Never released a damn thing waiting for this feature and that to be done #DevDiscuss
Avoiding feature creep needs clarity on vision for product. Eg. Basecamp is clear that it's PM software for small biz. If companies grow & request extra functionality they advise them to seek alternative products. Describe these customers as 'graduating' from Basecamp #DevDiscuss
I once built a pretty cool single-purpose search engine and feature/scope creeped it until I had a shitty Google on my hands. I learned a lot of valuable lessons from that failure. #DevDiscuss
While implementing a specific thing, more things to implement are requested, demanded, or discovered that would be nice to have but are not directly part of the current, specific thing. That's "feature creep" #DevDiscuss
I don't believe in Feature Creep. The very term implies you knew everything when you started (which you can't). It's what you learn along the way. #DevDiscuss.
Feature creep is when there's a feature for almost everything and more features being added under the impression it will help others but can take away from the user experience or project goals. #devdiscuss
If you're truly agile then "feature creep" isn't really a thing, is it? But if you are not agile (and, let's face it, most groups who say they are agile are actually not) that means you keep adding things before shipping. That's feature creep. #ShipMore#DevDiscuss
I don't believe in Feature Creep. The very term implies you knew everything when you started (which you can't). It's what you learn along the way. #DevDiscuss.
I don't believe in Feature Creep. The very term implies you knew everything when you started (which you can't). It's what you learn along the way. #DevDiscuss.
You have to have a set of features that make up version X of your project and have a GOOD reason for and changes or additions to that list. Some times there good reasons. Anything other than a GOOD reason is feature creep #DevDiscuss
For anyone wondering “wtf is feature creep?”
Day 1: Your boss wants you to build a a new payment form
Day 2: with a progress tracker
Day 10: that also notifies the user when their favorite song is on the radio.
#DevDiscuss
Feature creep? No problem. Let's add it to the backlog and let's review priorities. Moreover, the PO must remember to stakeholders that there is a roadmap and their "what if we add this?" may change it and delay other key features for the project #DevDiscuss
Feature creep and scope creep are technically different things but I think they both stem from problems with vision or management. I think experience goes a long way in developing a feel for this. I have no idea if I have "good feel" but it's improving #DevDiscuss
I think so. If it doesn't help with the intended goal or takes away from the user experience, unnecessary features can easily turn into feature creep. Developers have to be careful because what might seem like a good idea could create problems elsewhere #devdiscuss
I don't believe in Feature Creep. The very term implies you knew everything when you started (which you can't). It's what you learn along the way. #DevDiscuss.
Though as new features are discovered, how do you get paid for them beyond the original estimate?
(semi rhetorical, as "feature creep" is inevitable, it's better to build discovery and incremental feature additions into the billing structure)
#DevDiscuss
The remedies for feature/scope creep as I see it:
When you call all the shots: Long walks in the park mulling over the purpose of the project. Do this over and over again.
When it's a client's project: Communicating the risks of feature creep UP FRONT
#DevDiscuss
I have dealt with "feature creeps" in the past. It usually leads to what I like to call "Frankenstein products". I try to advise against it, but it doesn't always work.
#DevDiscuss
A friend of mine would re-start the full spec+quote process every time the client asked for a new feature. Didn't take long for the clients to stop the creep. #DevDiscuss
Feature creep: Implement exporting this data to an Excel spreadsheet using only this existing report as your guide asap! Who cares about easily editing the products we sell! #DevDiscuss
The hardest thing for me lately has been avoiding self-created feature creep. We're working on releasing a product and we set the scope of what the release would include - it's hard not to add those "nice to have" features that will make the project better #devdiscuss
Feature creep to me is adding in an additional feature that is not required for the operation of the application but something that would be "nice to have." Example: "wouldn't it be nice if there was a bulk upload feature to do this?" #DevDiscuss
In the end, it's so much better to document what those "nice to have" features are and get your release out the door! Writing good software is an ongoing process, and there will always be improvements you can make. Don't let perfect be the enemy of good! #devdiscuss
I strongly encourage them to think through their ideas and requests in detail and try to appreciate the wider touch points of a new feature. There’s also an inherent risk when the request comes with a stringent timeline. #DevDiscuss
Feature creep. Scope creep. Not keeping the main thing the main thing. Creates product bloat, lowers quality of experience, and crushes morale. #DevDiscuss
Identifying feature creep probably comes with experience and becomes easier to identify each time software is being built. I think the best way identifying feature creep is your own instincts. If you feel there's too much, chances are there is. #devdiscuss
While I understand what you're saying I think the term depends on the feature and project. Was this feature missed as a core business requirement? Or was this suggested only because it might be "cool" or help a few people out? #DevDiscuss
A lack of testing leads to longer manual test cycles, which leads to less frequent releases, which puts pressure on product management to release a feature now cause there months is too far away, which leads to feature creep. #DevDiscuss
Feature creep is a legacy of waterfall project management when companies didn't have ongoing, iterative deployment with constant feedback so they tend to ask for everything they could during the specification phase #devdiscuss
Feature creep can also be lumping in previously punted-on features while working on a related feature, but wasn't taken into consideration at the beginning of the project when scoping it out #DevDiscuss
My contracts with clients are very specific about what's included and what's not. If it's not written in the contract, it's not included. If features change, the contract is amended and the client pays up front for any additions. #DevDiscuss
Before leaping to design the feature (the "what" & "how"), try to shift the focus on "why?" and then quantify how you will measure the success of this expansion in capabilities. It's a good trick for discovering features that are for "kicks & giggles" 😂
#DevDiscuss
I have one! 👋
In case you missed it from earlier today, we launched Sustaining Memberships for https://t.co/XXYycIc87V, a way to support what we're up to and get the most out of being part of the community.
https://t.co/ou6IFKLvud#DevDiscuss
