¿Con qué podemos ayudarte?

Por ejemplo Diagramas de Gantt, Crear tareas, Compartir carpetas

Using Projects vs. Tasks for Website features

3 comentarios

  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Carolanne Mak

    (Editado )

    Hi @Al, 

    This sounds like a really cool way of structuring. The closest thing I can compare it to is the COE in my team's workspace - I created a main resources folder and added backlogged tasks to house entries on various topics. Then I added subfolders to group resources by types and help with search / navigation. So, for example, you could find a task entry for social selling under the main resources folder, and it would also be double-tagged to relevant subfolders, such as "trainings", "social media resources", etc. For me, tagging tasks to multiple folders was easier to work with than dealing with subtasks under parent tasks.

    Is there a reason you want to use projects for some features, rather than folders? I feel like folders and projects have many of the same options, but I chose subfolders because I didn't have start and end dates to consider. If applicable, you could use folders to show page hierarchy / organization that doesn't really change, and then include projects when you're actually looking to update certain features.

    Let me know what you think!

    Regards,
    Carolanne

    Is this helpful? 0
    Acciones de comentarios Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Al Sape

    Carolanne, thanks for responding to me.  I have since thought this through and I am thinking about using folders more readily as you suggest, with a more "pure" implementation of tagging tasks with the folders, which then allows me to take advantage of what is possibly the biggest plus of Wrike for me - the fact that tags are organized in Folders and hierarchies, whereas in other Project Management apps they are simply one big list.

    You also raise another point of how you enter backlogged tasks for various stuff.  One of the main reasons my team chose Wrike was the ability to enter just about "anything" we want to work on, be it a bug, an idea, a goal, etc. in relative quick fashion, then later discuss and figure out whether its a task, a project, a "goal" for which we'd have a folder and track long term, something like "reduce costs" etc.  Ideally I'd like to be able to transition these items to various data types, first and foremost from a task to an idea.  There's a big thread discussing this, which was even moved to "coming soon," but sadly, is no longer in that state:

    https://help.wrike.com/hc/en-us/community/posts/115000310005-Convert-a-Task-into-a-Project%20?page=5#comments

    I'd be curious as a fellow green belt to hear your take on this capability of Wrike.  Perhaps we can rally some support for this issue, it would be huge for me to see it released!

    Thanks again!

    Is this helpful? 0
    Acciones de comentarios Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Carolanne Mak

    @Al Yup, I've been following that request. While my team doesn't have many use cases for converting tasks to projects, it's likely because we've placed the burden on them to always define what they're going to need from the start. Happy to comment in that post with another example. 

    Is this helpful? 0
    Acciones de comentarios Permalink

Iniciar sesión para dejar un comentario.

Folllowing List for Post: Using Projects vs. Tasks for Website features
[this list is visible for admins and agents only]

Community

Welcome 🖖

Hi there! 🙂 Want to become a black belt Wrike Ninja? Here's how to earn a Wrike badge

Welcome 🖖 Have you checked out this week's Release Notes yet?

Hey! 👋 Curious about something? Visit How To to search and ask the Community for answers.

Welcome! 👋 Figured out a good tip or trick? Share it in Best Practices.

Want to connect your existing software to Wrike? Learn and ask how in the API section.